Skip to main content

Exasol

Test data in Exasol.

1. Install​

uv tool install --python python3.11 --upgrade 'datacontract-cli[exasol]'

See Installation for pip, pipx, and Docker.

2. Authenticate​

Create a .env file in your working directory (or export the variables):

# .env
DATACONTRACT_EXASOL_USERNAME=sys
DATACONTRACT_EXASOL_PASSWORD=mysecretpassword

The server certificate is verified against the system CA store; for a self-signed certificate, pin its fingerprint — see the Exasol Reference.

3. Describe the server in the contract​

The exasol server type was added in ODCS v3.2.0, so the contract has to declare apiVersion: v3.2.0. There is no datacontract import exasol yet: write the schema by hand, or start from a DDL script with datacontract import sql --source orders.sql --dialect postgres and replace the generated servers block.

apiVersion: v3.2.0
kind: DataContract
id: orders
version: 1.0.0
status: active
servers:
  - server: production
    type: exasol
    host: exasol.acme.com
    port: 8563
    schema: sales
schema:
  - name: orders
    properties:
      - name: order_id
        logicalType: integer
        physicalType: DECIMAL(18,0)
        primaryKey: true
      - name: order_total
        logicalType: number
        physicalType: DECIMAL(10,2)

host may be a cluster range (n11..14.acme.com).

4. Test the actual data​

datacontract test datacontract.yaml
Testing datacontract.yaml
Server: production (type=exasol, host=exasol.acme.com, port=8563, schema=sales)
╭────────┬───────────────────────────────────────────────────────────┬──────────┬─────────╮
│ Result │ Check                                                     │ Field    │ Details │
├────────┼───────────────────────────────────────────────────────────┼──────────┼─────────┤
│ passed │ Check that field 'order_id' is present                    │ order_id │         │
│ passed │ Check that field order_id has physical type DECIMAL(18,0) │ order_id │         │
│  ...   │                                                           │          │         │
╰────────┴───────────────────────────────────────────────────────────┴──────────┴─────────╯
🟢 Data contract is valid. Ran 6 checks. Took 1.4 seconds.

5. Let it catch a violation​

The contract becomes valuable when it detects drift. Tighten an expectation — for example, add a quality rule to a schema in datacontract.yaml:

schema:
  - name: orders
    # ...
    quality:
      - type: sql
        description: No order has a negative total
        query: SELECT COUNT(*) FROM orders WHERE order_total < 0
        mustBe: 0

Run datacontract test datacontract.yaml again: every violation is listed as an error, and the command exits with code 1 — ready for CI/CD and scheduled runs so you catch drift before your consumers do.

Reference​

All authentication options (including TLS) and the data type handling: Exasol Reference.

Troubleshooting​

  • Could not connect to Exasol: [SSL: CERTIFICATE_VERIFY_FAILED] — the cluster uses a certificate the system CA store does not know; pin it with DATACONTRACT_EXASOL_FINGERPRINT, see TLS.
  • Connection exception - schema ... not found — the schema in the servers block must exist, and a mixed-case schema created with quotes must be spelled exactly ("Sales" is not found by sales).