datacontract-cli 0.11.1__tar.gz → 0.11.2__tar.gz

{datacontract_cli-0.11.1/datacontract_cli.egg-info → datacontract_cli-0.11.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: datacontract-cli
-Version: 0.11.1
+Version: 0.11.2
 Summary: The datacontract CLI is an open source command-line tool for working with Data Contracts. It uses data contract YAML files to lint the data contract, connect to data sources and execute schema and quality tests, detect breaking changes, and export to different formats. The tool is written in Python. It can be used as a standalone CLI tool, in a CI/CD pipeline, or directly as a Python library.
 Author-email: Jochen Christ <jochen.christ@innoq.com>, Stefan Negele <stefan.negele@innoq.com>, Simon Harrer <simon.harrer@innoq.com>
 License-Expression: MIT
@@ -20,8 +20,8 @@ Requires-Dist: fastparquet<2025.0.0,>=2024.5.0
 Requires-Dist: numpy<2.0.0,>=1.26.4
 Requires-Dist: python-multipart<1.0.0,>=0.0.20
 Requires-Dist: rich<15.0,>=13.7
-Requires-Dist: sqlglot<28.0.0,>=26.6.0
-Requires-Dist: duckdb<2.0.0,>=1.0.0
+Requires-Dist: sqlglot<29.0.0,>=26.6.0
+Requires-Dist: duckdb<1.4.0,>=1.0.0
 Requires-Dist: soda-core-duckdb<3.6.0,>=3.3.20
 Requires-Dist: setuptools>=60
 Requires-Dist: python-dotenv<2.0.0,>=1.0.0
@@ -41,7 +41,7 @@ Requires-Dist: openpyxl<4.0.0,>=3.1.5; extra == "excel"
 Provides-Extra: databricks
 Requires-Dist: soda-core-spark-df<3.6.0,>=3.3.20; extra == "databricks"
 Requires-Dist: soda-core-spark[databricks]<3.6.0,>=3.3.20; extra == "databricks"
-Requires-Dist: databricks-sql-connector<4.2.0,>=3.7.0; extra == "databricks"
+Requires-Dist: databricks-sql-connector<4.3.0,>=3.7.0; extra == "databricks"
 Requires-Dist: databricks-sdk<0.74.0; extra == "databricks"
 Requires-Dist: pyspark<4.0.0,>=3.5.5; extra == "databricks"
 Provides-Extra: iceberg
@@ -56,7 +56,7 @@ Provides-Extra: s3
 Requires-Dist: s3fs<2026.0.0,>=2025.2.0; extra == "s3"
 Requires-Dist: aiobotocore<2.26.0,>=2.17.0; extra == "s3"
 Provides-Extra: snowflake
-Requires-Dist: snowflake-connector-python[pandas]<4.1,>=3.6; extra == "snowflake"
+Requires-Dist: snowflake-connector-python[pandas]<4.2,>=3.6; extra == "snowflake"
 Requires-Dist: soda-core-snowflake<3.6.0,>=3.3.20; extra == "snowflake"
 Provides-Extra: sqlserver
 Requires-Dist: soda-core-sqlserver<3.6.0,>=3.3.20; extra == "sqlserver"
@@ -86,9 +86,9 @@ Requires-Dist: datacontract-cli[all]; extra == "dev"
 Requires-Dist: httpx==0.28.1; extra == "dev"
 Requires-Dist: kafka-python; extra == "dev"
 Requires-Dist: minio==7.2.17; extra == "dev"
-Requires-Dist: moto==5.1.17; extra == "dev"
+Requires-Dist: moto==5.1.18; extra == "dev"
 Requires-Dist: pandas>=2.1.0; extra == "dev"
-Requires-Dist: pre-commit<4.5.0,>=3.7.1; extra == "dev"
+Requires-Dist: pre-commit<4.6.0,>=3.7.1; extra == "dev"
 Requires-Dist: pytest; extra == "dev"
 Requires-Dist: pytest-xdist; extra == "dev"
 Requires-Dist: pymssql==2.3.9; extra == "dev"
@@ -120,7 +120,7 @@ It can be used as a standalone CLI tool, in a CI/CD pipeline, or directly as a P
 Let's look at this data contract:
 [https://datacontract.com/orders-v1.odcs.yaml](https://datacontract.com/orders-v1.odcs.yaml)
 
-We have a _servers_ section with endpoint details to a Postgres database, _schema_ for the structure and semantics of the data, _slaAttributes_ and _quality_ attributes that describe the expected freshness and number of rows.
+We have a _servers_ section with endpoint details to a Postgres database, _schema_ for the structure and semantics of the data, _service levels_ and _quality_ attributes that describe the expected freshness and number of rows.
 
 This data contract contains all information to connect to the database and check that the actual data meets the defined schema specification and quality expectations.
 We can use this information to test if the actual data product is compliant to the data contract.
@@ -342,6 +342,7 @@ A list of available extras:
 | Snowflake Integration   | `pip install datacontract-cli[snowflake]`  |
 | Microsoft SQL Server    | `pip install datacontract-cli[sqlserver]`  |
 | Trino                   | `pip install datacontract-cli[trino]`      |
+| Impala                  | `pip install datacontract-cli[impala]` 	   |
 | dbt                     | `pip install datacontract-cli[dbt]`        |
 | DBML                    | `pip install datacontract-cli[dbml]`       |
 | Parquet                 | `pip install datacontract-cli[parquet]`    |
@@ -493,6 +494,7 @@ Supported server types:
 - [kafka](#kafka)
 - [postgres](#postgres)
 - [trino](#trino)
+- [impala](#impala)
 - [api](#api)
 - [local](#local)
 
@@ -1023,6 +1025,53 @@ models:
 | `DATACONTRACT_TRINO_PASSWORD` | `mysecretpassword` | Password    |
 
 
+#### Impala
+
+Data Contract CLI can run Soda checks against an Apache Impala cluster.
+
+##### Example
+
+datacontract.yaml
+```yaml
+servers:
+  impala:
+    type: impala
+    host: my-impala-host
+    port: 443
+    # Optional default database used for Soda scans
+    database: my_database
+models:
+  my_table_1: # corresponds to a table
+    type: table
+    # fields as usual …
+```
+
+##### Environment Variables
+
+| Environment Variable                      | Example               | Description                                               |
+|-------------------------------            |--------------------   |-------------                                              |
+| `DATACONTRACT_IMPALA_USERNAME`            | `analytics_user`      | Username used to connect to Impala                        |
+| `DATACONTRACT_IMPALA_PASSWORD`            | `mysecretpassword`    | Password for the Impala user                              |
+| `DATACONTRACT_IMPALA_USE_SSL`             | `true`                | Whether to use SSL; defaults to true if unset             |
+| `DATACONTRACT_IMPALA_AUTH_MECHANISM`      | `LDAP`                | Authentication mechanism; defaults to LDAP                |
+| `DATACONTRACT_IMPALA_USE_HTTP_TRANSPORT`  | `true`                | Whether to use the HTTP transport; defaults to true       |
+| `DATACONTRACT_IMPALA_HTTP_PATH`           | `cliservice`          | HTTP path for the Impala service; defaults to cliservice  |
+
+### Type-mapping note (logicalType → Impala type)
+
+If `physicalType` is not specified in the schema, we recommend the following mapping from `logicalType` to Impala column types:
+
+|logicalType | Recommended Impala type |
+|------------|-------------------------|
+| `integer`  | `INT` or `BIGINT`       |
+| `number`   | `DOUBLE`/`decimal(..)`  |
+| `string`   | `STRING` or `VARCHAR`   |
+| `boolean`  | `BOOLEAN`               |
+| `date`     | `DATE`                  |
+| `datetime` | `TIMESTAMP`             |
+
+This keeps the Impala schema compatible with the expectations of the Soda checks generated by datacontract-cli.
+
 #### API
 
 Data Contract CLI can test APIs that return data in JSON format. 
@@ -1569,38 +1618,25 @@ datacontract import --format sql --source my_ddl.sql --dialect postgres --output
 
 Available import options:
 
-| Type               | Description                                    | Status |
-|--------------------|------------------------------------------------|--------|
-| `avro`             | Import from AVRO schemas                       | ✅      |
-| `bigquery`         | Import from BigQuery Schemas                   | ✅      |
-| `csv`              | Import from CSV File                           | ✅      |
-| `dbml`             | Import from DBML models                        | ✅      |
-| `dbt`              | Import from dbt models                         | ✅      |
-| `excel`            | Import from ODCS Excel Template                | ✅      |
-| `glue`             | Import from AWS Glue DataCatalog               | ✅      |
-| `iceberg`          | Import from an Iceberg JSON Schema Definition  | partial |
-| `jsonschema`       | Import from JSON Schemas                       | ✅      |
-| `odcs`             | Import from Open Data Contract Standard (ODCS) | ✅      |
-| `parquet`          | Import from Parquet File Metadata              | ✅      |
-| `protobuf`         | Import from Protobuf schemas                   | ✅      |
-| `spark`            | Import from Spark StructTypes, Variant         | ✅      |
-| `sql`              | Import from SQL DDL                            | ✅      |
-| `unity`            | Import from Databricks Unity Catalog           | partial |
-| `excel`            | Import from ODCS Excel Template                | ✅      |
-| Missing something? | Please create an issue on GitHub               | TBD     |
-
-
-#### ODCS
-
-Import from Open Data Contract Standard (ODCS) v2 or v3.
-The importer automatically detects the ODCS version and imports the data contract.
-
-Examples:
+| Type               | Description                                   | Status  |
+|--------------------|-----------------------------------------------|---------|
+| `avro`             | Import from AVRO schemas                      | ✅       |
+| `bigquery`         | Import from BigQuery Schemas                  | ✅       |
+| `csv`              | Import from CSV File                          | ✅       |
+| `dbml`             | Import from DBML models                       | ✅       |
+| `dbt`              | Import from dbt models                        | ✅       |
+| `excel`            | Import from ODCS Excel Template               | ✅       |
+| `glue`             | Import from AWS Glue DataCatalog              | ✅       |
+| `iceberg`          | Import from an Iceberg JSON Schema Definition | partial |
+| `jsonschema`       | Import from JSON Schemas                      | ✅       |
+| `parquet`          | Import from Parquet File Metadata             | ✅       |
+| `protobuf`         | Import from Protobuf schemas                  | ✅       |
+| `spark`            | Import from Spark StructTypes, Variant        | ✅       |
+| `sql`              | Import from SQL DDL                           | ✅       |
+| `unity`            | Import from Databricks Unity Catalog          | partial |
+| `excel`            | Import from ODCS Excel Template               | ✅       |
+| Missing something? | Please create an issue on GitHub              | TBD     |
 
-```bash
-# Example import from ODCS
-datacontract import --format odcs --source my_data_contract.odcs.yaml
-```
 
 #### BigQuery
 
@@ -2202,8 +2238,7 @@ We are happy to receive your contributions. Propose your change in an issue or d
 
 ## Related Tools
 
-- [Data Contract Manager](https://www.datacontract-manager.com/) is a commercial tool to manage data contracts. It contains a web UI, access management, and data governance for a full enterprise data marketplace.
-- [Data Contract GPT](https://gpt.datacontract.com) is a custom GPT that can help you write data contracts.
+- [Entropy Data](https://www.entropy-data.com/) is a commercial tool to manage data contracts. It contains a web UI, access management, and data governance for a data product marketplace based on data contracts.
 - [Data Contract Editor](https://editor.datacontract.com) is an editor for Data Contracts, including a live html preview.
 - [Data Contract Playground](https://data-catering.github.io/data-contract-playground/) allows you to validate and export your data contract to different formats within your browser.
 

{datacontract_cli-0.11.1 → datacontract_cli-0.11.2}/README.md

@@ -21,7 +21,7 @@ It can be used as a standalone CLI tool, in a CI/CD pipeline, or directly as a P
 Let's look at this data contract:
 [https://datacontract.com/orders-v1.odcs.yaml](https://datacontract.com/orders-v1.odcs.yaml)
 
-We have a _servers_ section with endpoint details to a Postgres database, _schema_ for the structure and semantics of the data, _slaAttributes_ and _quality_ attributes that describe the expected freshness and number of rows.
+We have a _servers_ section with endpoint details to a Postgres database, _schema_ for the structure and semantics of the data, _service levels_ and _quality_ attributes that describe the expected freshness and number of rows.
 
 This data contract contains all information to connect to the database and check that the actual data meets the defined schema specification and quality expectations.
 We can use this information to test if the actual data product is compliant to the data contract.
@@ -243,6 +243,7 @@ A list of available extras:
 | Snowflake Integration   | `pip install datacontract-cli[snowflake]`  |
 | Microsoft SQL Server    | `pip install datacontract-cli[sqlserver]`  |
 | Trino                   | `pip install datacontract-cli[trino]`      |
+| Impala                  | `pip install datacontract-cli[impala]` 	   |
 | dbt                     | `pip install datacontract-cli[dbt]`        |
 | DBML                    | `pip install datacontract-cli[dbml]`       |
 | Parquet                 | `pip install datacontract-cli[parquet]`    |
@@ -394,6 +395,7 @@ Supported server types:
 - [kafka](#kafka)
 - [postgres](#postgres)
 - [trino](#trino)
+- [impala](#impala)
 - [api](#api)
 - [local](#local)
 
@@ -924,6 +926,53 @@ models:
 | `DATACONTRACT_TRINO_PASSWORD` | `mysecretpassword` | Password    |
 
 
+#### Impala
+
+Data Contract CLI can run Soda checks against an Apache Impala cluster.
+
+##### Example
+
+datacontract.yaml
+```yaml
+servers:
+  impala:
+    type: impala
+    host: my-impala-host
+    port: 443
+    # Optional default database used for Soda scans
+    database: my_database
+models:
+  my_table_1: # corresponds to a table
+    type: table
+    # fields as usual …
+```
+
+##### Environment Variables
+
+| Environment Variable                      | Example               | Description                                               |
+|-------------------------------            |--------------------   |-------------                                              |
+| `DATACONTRACT_IMPALA_USERNAME`            | `analytics_user`      | Username used to connect to Impala                        |
+| `DATACONTRACT_IMPALA_PASSWORD`            | `mysecretpassword`    | Password for the Impala user                              |
+| `DATACONTRACT_IMPALA_USE_SSL`             | `true`                | Whether to use SSL; defaults to true if unset             |
+| `DATACONTRACT_IMPALA_AUTH_MECHANISM`      | `LDAP`                | Authentication mechanism; defaults to LDAP                |
+| `DATACONTRACT_IMPALA_USE_HTTP_TRANSPORT`  | `true`                | Whether to use the HTTP transport; defaults to true       |
+| `DATACONTRACT_IMPALA_HTTP_PATH`           | `cliservice`          | HTTP path for the Impala service; defaults to cliservice  |
+
+### Type-mapping note (logicalType → Impala type)
+
+If `physicalType` is not specified in the schema, we recommend the following mapping from `logicalType` to Impala column types:
+
+|logicalType | Recommended Impala type |
+|------------|-------------------------|
+| `integer`  | `INT` or `BIGINT`       |
+| `number`   | `DOUBLE`/`decimal(..)`  |
+| `string`   | `STRING` or `VARCHAR`   |
+| `boolean`  | `BOOLEAN`               |
+| `date`     | `DATE`                  |
+| `datetime` | `TIMESTAMP`             |
+
+This keeps the Impala schema compatible with the expectations of the Soda checks generated by datacontract-cli.
+
 #### API
 
 Data Contract CLI can test APIs that return data in JSON format. 
@@ -1470,38 +1519,25 @@ datacontract import --format sql --source my_ddl.sql --dialect postgres --output
 
 Available import options:
 
-| Type               | Description                                    | Status |
-|--------------------|------------------------------------------------|--------|
-| `avro`             | Import from AVRO schemas                       | ✅      |
-| `bigquery`         | Import from BigQuery Schemas                   | ✅      |
-| `csv`              | Import from CSV File                           | ✅      |
-| `dbml`             | Import from DBML models                        | ✅      |
-| `dbt`              | Import from dbt models                         | ✅      |
-| `excel`            | Import from ODCS Excel Template                | ✅      |
-| `glue`             | Import from AWS Glue DataCatalog               | ✅      |
-| `iceberg`          | Import from an Iceberg JSON Schema Definition  | partial |
-| `jsonschema`       | Import from JSON Schemas                       | ✅      |
-| `odcs`             | Import from Open Data Contract Standard (ODCS) | ✅      |
-| `parquet`          | Import from Parquet File Metadata              | ✅      |
-| `protobuf`         | Import from Protobuf schemas                   | ✅      |
-| `spark`            | Import from Spark StructTypes, Variant         | ✅      |
-| `sql`              | Import from SQL DDL                            | ✅      |
-| `unity`            | Import from Databricks Unity Catalog           | partial |
-| `excel`            | Import from ODCS Excel Template                | ✅      |
-| Missing something? | Please create an issue on GitHub               | TBD     |
-
-
-#### ODCS
-
-Import from Open Data Contract Standard (ODCS) v2 or v3.
-The importer automatically detects the ODCS version and imports the data contract.
-
-Examples:
+| Type               | Description                                   | Status  |
+|--------------------|-----------------------------------------------|---------|
+| `avro`             | Import from AVRO schemas                      | ✅       |
+| `bigquery`         | Import from BigQuery Schemas                  | ✅       |
+| `csv`              | Import from CSV File                          | ✅       |
+| `dbml`             | Import from DBML models                       | ✅       |
+| `dbt`              | Import from dbt models                        | ✅       |
+| `excel`            | Import from ODCS Excel Template               | ✅       |
+| `glue`             | Import from AWS Glue DataCatalog              | ✅       |
+| `iceberg`          | Import from an Iceberg JSON Schema Definition | partial |
+| `jsonschema`       | Import from JSON Schemas                      | ✅       |
+| `parquet`          | Import from Parquet File Metadata             | ✅       |
+| `protobuf`         | Import from Protobuf schemas                  | ✅       |
+| `spark`            | Import from Spark StructTypes, Variant        | ✅       |
+| `sql`              | Import from SQL DDL                           | ✅       |
+| `unity`            | Import from Databricks Unity Catalog          | partial |
+| `excel`            | Import from ODCS Excel Template               | ✅       |
+| Missing something? | Please create an issue on GitHub              | TBD     |
 
-```bash
-# Example import from ODCS
-datacontract import --format odcs --source my_data_contract.odcs.yaml
-```
 
 #### BigQuery
 
@@ -2103,8 +2139,7 @@ We are happy to receive your contributions. Propose your change in an issue or d
 
 ## Related Tools
 
-- [Data Contract Manager](https://www.datacontract-manager.com/) is a commercial tool to manage data contracts. It contains a web UI, access management, and data governance for a full enterprise data marketplace.
-- [Data Contract GPT](https://gpt.datacontract.com) is a custom GPT that can help you write data contracts.
+- [Entropy Data](https://www.entropy-data.com/) is a commercial tool to manage data contracts. It contains a web UI, access management, and data governance for a data product marketplace based on data contracts.
 - [Data Contract Editor](https://editor.datacontract.com) is an editor for Data Contracts, including a live html preview.
 - [Data Contract Playground](https://data-catering.github.io/data-contract-playground/) allows you to validate and export your data contract to different formats within your browser.
 

{datacontract_cli-0.11.1 → datacontract_cli-0.11.2}/datacontract/engines/soda/check_soda_execute.py

@@ -14,6 +14,7 @@ from open_data_contract_standard.model import OpenDataContractStandard, Server
 from datacontract.engines.soda.connections.bigquery import to_bigquery_soda_configuration
 from datacontract.engines.soda.connections.databricks import to_databricks_soda_configuration
 from datacontract.engines.soda.connections.duckdb_connection import get_duckdb_connection
+from datacontract.engines.soda.connections.impala import to_impala_soda_configuration
 from datacontract.engines.soda.connections.kafka import create_spark_session, read_kafka_topic
 from datacontract.engines.soda.connections.postgres import to_postgres_soda_configuration
 from datacontract.engines.soda.connections.snowflake import to_snowflake_soda_configuration
@@ -95,6 +96,18 @@ def check_soda_execute(
             logging.info("Use Spark to connect to data source")
             scan.add_spark_session(spark, data_source_name="datacontract-cli")
             scan.set_data_source_name("datacontract-cli")
+    
+    # ------------------------------------------------------------------
+    # NEW: native Impala server type
+    # ------------------------------------------------------------------
+    elif server.type == "impala":
+        run.log_info("Connecting to Impala via Soda engine")
+        soda_configuration_str = to_impala_soda_configuration(server)
+        scan.add_configuration_yaml_str(soda_configuration_str)
+        # data source name must match what we configure in to_impala_soda_configuration
+        scan.set_data_source_name("impala")
+
+    
     elif server.type == "kafka":
         if spark is None:
             spark = create_spark_session()
@@ -218,4 +231,4 @@ def update_reason(check, c):
                 # print(check.reason)
             break  # Exit the loop once the desired block is found
     if "fail" in c["diagnostics"]:
-        check.reason = f"Value: {c['diagnostics']['value']} Fail: {c['diagnostics']['fail']}"
+        check.reason = f"Value: {c['diagnostics']['value']} Fail: {c['diagnostics']['fail']}"

datacontract_cli-0.11.2/datacontract/engines/soda/connections/impala.py

@@ -0,0 +1,74 @@
+import os
+
+import yaml
+
+
+def _get_bool_env(name: str, default: bool) -> bool:
+    """
+    Helper to read a boolean from an environment variable.
+
+    Accepts: 1/0, true/false, yes/no, on/off (case-insensitive).
+    """
+    value = os.getenv(name)
+    if value is None:
+        return default
+    return value.strip().lower() in ("1", "true", "yes", "y", "on")
+
+
+def to_impala_soda_configuration(server):
+    """
+    Build a Soda configuration for an Impala data source.
+
+    Expects the datacontract `server` block to have at least:
+      - type   (e.g. "impala")
+      - host
+      - port   (optional; defaults to 443 if not set)
+
+    Credentials are taken from environment variables:
+      - DATACONTRACT_IMPALA_USERNAME
+      - DATACONTRACT_IMPALA_PASSWORD
+
+    Connection behaviour can be overridden via:
+      - DATACONTRACT_IMPALA_USE_SSL            (default: true)
+      - DATACONTRACT_IMPALA_AUTH_MECHANISM     (default: "LDAP")
+      - DATACONTRACT_IMPALA_USE_HTTP_TRANSPORT (default: true)
+      - DATACONTRACT_IMPALA_HTTP_PATH          (default: "cliservice")
+    """
+
+    port = getattr(server, "port", None)
+    if port is None:
+        port = 443
+
+    # Optional database / schema default, e.g. "edpdevs_scratch"
+    database = getattr(server, "database", None)
+
+    use_ssl = _get_bool_env("DATACONTRACT_IMPALA_USE_SSL", True)
+    auth_mechanism = os.getenv("DATACONTRACT_IMPALA_AUTH_MECHANISM", "LDAP")
+    use_http_transport = _get_bool_env(
+        "DATACONTRACT_IMPALA_USE_HTTP_TRANSPORT", True
+    )
+    http_path = os.getenv("DATACONTRACT_IMPALA_HTTP_PATH", "cliservice")
+
+    connection = {
+        "host": server.host,
+        "port": str(port),
+        "username": os.getenv("DATACONTRACT_IMPALA_USERNAME"),
+        "password": os.getenv("DATACONTRACT_IMPALA_PASSWORD"),
+        "use_ssl": use_ssl,
+        "auth_mechanism": auth_mechanism,
+        "use_http_transport": use_http_transport,
+        "http_path": http_path,
+    }
+
+    if database:
+        connection["database"] = database
+
+    soda_configuration = {
+        f"data_source {server.type}": {
+            "type": "impala",
+            "connection": connection,
+        }
+    }
+
+    soda_configuration_str = yaml.dump(soda_configuration)
+    return soda_configuration_str

{datacontract_cli-0.11.1 → datacontract_cli-0.11.2}/datacontract/export/sql_type_converter.py

@@ -518,6 +518,64 @@ def convert_type_to_trino(field: Union[SchemaProperty, FieldLike]) -> None | str
     return None
 
 
+def convert_type_to_impala(field: Union[SchemaProperty, FieldLike]) -> None | str:
+    """Convert from supported data contract types to equivalent Impala types.
+
+    Used as a fallback when `physicalType` is not present.
+    """
+    # Allow an explicit override via config/customProperties
+    impala_type = _get_config_value(field, "impalaType")
+    if impala_type:
+        return impala_type
+
+    field_type = _get_type(field)
+    if not field_type:
+        return None
+
+    t = field_type.lower()
+
+    # String-like
+    if t in ["string", "varchar", "text"]:
+        return "STRING"
+
+    # Numeric / decimal
+    if t in ["number", "decimal", "numeric"]:
+        precision = _get_precision(field) or 38
+        scale = _get_scale(field) or 0
+        return f"DECIMAL({precision},{scale})"
+
+    if t == "float":
+        return "FLOAT"
+    if t == "double":
+        return "DOUBLE"
+
+    # Integers
+    if t in ["integer", "int"]:
+        return "INT"
+    if t in ["long", "bigint"]:
+        return "BIGINT"
+
+    # Boolean
+    if t == "boolean":
+        return "BOOLEAN"
+
+    # Temporal – Impala has a single TIMESTAMP type
+    if t in ["timestamp", "timestamp_ntz", "timestamp_tz"]:
+        return "TIMESTAMP"
+    if t == "date":
+        return "DATE"
+    # No dedicated TIME type in Impala → store as string
+    if t == "time":
+        return "STRING"
+
+    # Binary
+    if t in ["bytes", "binary"]:
+        return "BINARY"
+
+    # For complex / JSON-like types we currently do not emit a type check
+    # (returning None means no "has type" check is generated)
+    return None
+
 def convert_type_to_oracle(schema_property: SchemaProperty) -> None | str:
     """Convert ODCS logical types to Oracle types.
 
@@ -547,4 +605,4 @@ def convert_type_to_oracle(schema_property: SchemaProperty) -> None | str:
         "array": "CLOB",
     }
 
-    return mapping.get(logical_type)
+    return mapping.get(logical_type)