datacontract/datacontract-cli

(I hit this problem and asked Gemini to generate the bug report - so written by AI, but I've reviewed and it's got all the right info IMHO.) Title: ClickHouse SQL export does not escape apostrophes in column comments Bug report: Using Data Contract CLI 1.2.4, a valid contract with an apostrophe in a property description generates invalid ClickHouse SQL. Minimal reproduction (datacontract.yaml): apiVersion: v3.2.0 kind: DataContract id: urn:datacontract:quote-repro name: quote-repro version: 1.0.0 status: active schema: - name: example properties: - name: id logicalType: string required: true primaryKey: true - name: amount logicalType: number description: The extractor's amount. Run: datacontract lint datacontract.yaml datacontract export sql datacontract.yaml --dialect clickhouse --clickhouse-engine MergeTree Lint passes, but the export contains: `amount` Nullable(Decimal(38,0)) COMMENT 'The extractor's amount.' The apostrophe

When running the datacontract test command, only the result of the first test is displayed (I noticed this during the freshness checks). From the second test onwards, the result is always NULL. Is this a bug, or am I misunderstanding something? Datacontract Example slaProperties: slaProperties: id: monitoring_airflow_dag_task_contract_freshness property: freshness value: 4 unit: hour element: monitoring_airflow_dag_task_contract.dag_run_start_date description: The DAG metadata history must be up to date within 4 hours. id: monitoring_data_contract_check_freshness property: freshness value: 4 unit: hour element: monitoring_data_contract_check.check_timestamp description: The most recent execution of a Data Contract Check must not be more than 4 hours old. Output datacontract cli: ╭────────┬───────────────────────────────────────────────────────────

process_s3_file (datacontract/engines/fastjsonschema/check_jsonschema.py:202-217) validates only the last object matched by the location glob. Every other file is downloaded and then discarded unvalidated, so an invalid record in any file but the last goes unreported and the run still appends the passed check "All JSON entries are valid." for the model. Cause: the loop body only assigns a lazy generator over the current file's content to json_stream, overwriting the previous file's generator before anything consumes it; validate_json_stream is then called once, after the loop. Applies whenever location matches more than one object — e.g. the documented s3://my-bucket/orders/*.json, or a {model} pattern expanding onto several files. Secondary effect: the full dataset is downloaded (and paid for in egress) even though only one file is checked. Fix direction: validate inside the loop and accumulate the exceptions across files. Where to start: the fix is in process_s3_file — call valid

Dear team, I've noticed that when exporting an ODCS schema to avro or jsonschema, it uses the name of the objects and properties and ignores the physicalName. Commands used: datacontract export jsonschema --output jsonschema.json datacontract.yaml datacontract export avro --output avro.json datacontract.yaml ODCS Property: - name: Equipment Name physicalName: name logicalType: string description: Equipment name based on the ISA-95 model Result (avro): { "name": "Equipment Name", "doc": "Equipment name based on the ISA-95 model", "type": "string" }, Expected result: { "name": "name", "doc": "Equipment name based on the ISA-95 model", "type": "string" }, This problem extends to any datacontract test that checks a JSON using the json schema (e.g., when testing an HTTP API).