# export great-expectations

> Export a data contract to Great Expectations suite.

# `datacontract export great-expectations`

{/* AUTOGENERATED from `datacontract --help`: do not edit by hand; regenerate with update_command_docs.py */}

Export a data contract to Great Expectations suite.

```bash
datacontract export great-expectations [OPTIONS] [LOCATION]
```

| Argument | Default | Description |
|---|---|---|
| `[LOCATION]` | `datacontract.yaml` | The location (url or path) of the data contract yaml. |

| Option | Default | Description |
|---|---|---|
| `--engine` | — | The engine used for Great Expectations run. |
| `--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 external references (currently: authoritativeDefinitions\[type in \{definition, semantics\}]) in the contract and inline the fetched content from the configured entropy-data host. |
| `--debug` / `--no-debug` | — | Enable debug logging |

```bash
datacontract export great-expectations datacontract.yaml --engine sql --dialect postgres --output expectations.json
```

Guide: **[Export: Great Expectations](../../exports/great-expectations.md)**.