datacontract export sql
Export a data contract to SQL DDL.
datacontract export sql [OPTIONS] [LOCATION]
| Argument | Default | Description |
|---|---|---|
[LOCATION] | datacontract.yaml | The location (url, s3 url, or local path) of the data contract yaml. |
| Option | Default | Description |
|---|---|---|
--dialect | auto | The SQL dialect. Use auto (default) to detect the SQL dialect via the specified servers in the data contract. |
--output | — | File path where the exported data will be saved. If not provided, it will be printed to stdout. |
--server | — | The server name to export. |
--schema-name | all | Which schema to export, e.g., orders, or all for all schemas (default). |
--json-schema | — | The location (url or path) of the ODCS JSON Schema. |
--inline-references / --no-inline-references | --inline-references | Resolve authoritativeDefinitions of type definition, semantics or businessDefinition and inline them into the contract. Relative URLs and semantics IRIs are looked up on the ENTROPY_DATA_HOST (default https://api.entropy-data.com), other URLs are fetched directly, file references are read from disk. See https://cli.datacontract.com/semantics |
--clickhouse-engine | — | The ClickHouse table engine. Default: MergeTree(). Example: ReplicatedMergeTree('/clickhouse/tables/{shard}/table', '{replica}') |
--clickhouse-order-by | — | ORDER BY columns for ClickHouse (comma-separated). ClickHouse uses ORDER BY as its primary/sorting key (not PRIMARY KEY). Default: primary key columns if defined, omitted otherwise. Example: --clickhouse-order-by "event_date DESC, event_id" |
--debug / --no-debug | — | Enable debug logging |
datacontract export sql datacontract.yaml --dialect postgres --output ddl.sql
Guide: Export: SQL DDL.