Missing "Server" and "SLA" sections in the generated dataContractSpecification YAML file when converted from ODCS - Excel Template

[Akpozi]

Thanks for this datacontract cli tool. It has been very useful in upskilling my knowledge on data contracts.

I am now working on converting ODCS - Excel Template to dataContractSpecification YAML file

I have noticed that originally, the conversion of the (ODCS) - Excel Template using the line below generated the ODCS - YAML Template

!datacontract import --format excel --source ./shipments/shipments_odcs.xlsx --output ./shipments/shipments_odcs.yaml

However, recently, I observed that it directly generates the DataContractSpecification file.

The main issue I want to raise it that in the "ODCS - Excel Template" the SLA sheet and Server sheet does not get converted and populated in the generated dataContractSpecification YAML file when the Server used is "databricks". However, it works fine when "bigquery" is specified as the server.

A "WARNING" is produced when I run the below line to convert the ODCS - Excel Template to DataContractSpecification YAML file
!datacontract import --format excel --source ./shipments/shipments_odcs.xlsx --output ./shipments/shipments_datacontract.yaml

WARNING:datacontract.imports.excel_importer:Error importing servers: "Server" object has no field "schema"
Written result to misswin_products/products_datacontract_new.yaml

The generated dataContractSpecification file does not have Server and SLA sections - when "databricks" is specified as the Server. This happens for other server types that requires the "Schema" field.

Kindly advice on this. Thank you very much.

Regards,
Akpo

[gautierc-thelio]

Happens also with Trino server type.

[jochenchrist]

Problem identified: The code tried to set a pydantic property schema (which is a Python internal property....), it must be schema_.

[Akpozi]

Thank you @jochenchrist for the fix.