OpenMetadata/openmetadata-docs/content/v1.4.x/connectors/database/impala/index.md

title	slug
Impala	/connectors/database/impala

{% connectorDetailsHeader name="Impala" stage="PROD" platform="OpenMetadata" availableFeatures=["Metadata", "Data Profiler", "Data Quality", "dbt"] unavailableFeatures=["Query Usage", "Owners", "Lineage", "Column-level Lineage", "Tags", "Stored Procedures"] / %}

In this section, we provide guides and references to use the Impala connector.

Configure and schedule Impala metadata and profiler workflows from the OpenMetadata UI:

• Metadata Ingestion
• Data Profiler
• Data Quality
• dbt Integration
• Enable Security

{% partial file="/v1.4/connectors/ingestion-modes-tiles.md" variables={yamlPath: "/connectors/database/impala/yaml"} /%}

Metadata Ingestion

{% partial file="/v1.4/connectors/metadata-ingestion-ui.md" variables={ connector: "Impala", selectServicePath: "/images/v1.4/connectors/impala/select-service.png", addNewServicePath: "/images/v1.4/connectors/impala/add-new-service.png", serviceConnectionPath: "/images/v1.4/connectors/impala/service-connection.png", } /%}

{% stepsContainer %} {% extraContent parentTagName="stepsContainer" %}

Connection Details

• username: Specify the User to connect to Impala. It should have enough privileges to read all the metadata.
• password: Password to connect to Impala.
• hostPort: Enter the fully qualified hostname and port number for your Impala deployment in the Host and Port field.
• authMechanism: This parameter specifies the authentication method to use when connecting to the Impala server. Possible values are NOSASL, PLAIN, GSSAPI, LDAP, JWT. If you are using Kerberos authentication, you should set auth to GSSAPI.
• kerberosServiceName: This parameter specifies the Kerberos service name to use for authentication. This should only be specified if using Kerberos authentication.
• databaseSchema: Schema of the data source. This is optional parameter, if you would like to restrict the metadata reading to a single schema. When left blank, OpenMetadata Ingestion attempts to scan all the schemas.
• databaseName: In OpenMetadata, the Database Service hierarchy works as follows: Database Service > Database > Schema > Table. In the case of Impala, we won't have a Database as such. If you'd like to see your data in a database named something other than default, you can specify the name in this field.
• useSSL: Establish secure connection with Impala. Enables SSL for the connector.
• authOptions: Enter the auth options string for impala connection.

{% partial file="/v1.4/connectors/database/advanced-configuration.md" /%}

{% /extraContent %}

{% partial file="/v1.4/connectors/test-connection.md" /%}

{% partial file="/v1.4/connectors/database/configure-ingestion.md" /%}

{% partial file="/v1.4/connectors/ingestion-schedule-and-deploy.md" /%}

{% /stepsContainer %}

Securing Impala Connection with SSL in OpenMetadata

To configure SSL for secure connections between OpenMetadata and an Impala database, add the key use_ssl with a value of true to the connectionArguments to enable SSL. Additionally, include the key ca_cert with the path to the CA certificate file as its value. Ensure that the certificate file is accessible by the server, and if deploying via Docker or Kubernetes, update the CA certificate in the OpenMetadata server to reflect these changes.

{% image src="/images/v1.4/connectors/ssl_Impala.png" alt="SSL Configuration" height="450px" caption="SSL Configuration" /%}

{% partial file="/v1.4/connectors/troubleshooting.md" /%}

{% partial file="/v1.4/connectors/database/related.md" /%}