> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/connectors/connector-repositories/big-data-platform/qubole-hive.md). # Qubole Hive ## Connectivity Summary An out of the box connector is available for Qubole Hive databases. It provides support for crawling database objects, profiling of sample data and lineage building. > The connectivity to Qubole Hive is via JDBC driver, which is included in the platform. The connector currently supports the following versions of Qubole Hive: > **Edition:** no-awssdk > > **Version:** 1.0x The drivers used by the connector are given below: > **Driver / API:** Qubole Hive JDBC Driver > > **Version:** 1.0 (Latest version is 2.0) > > **Details:** Is JDBC 1.0 [https://s3.amazonaws.com/Qubole Hive-downloads/drivers/jdbc/1.2.41.1065/Qubole HiveJDBC42-no-awssdk-1.2.41.1065.jar](https://s3.amazonaws.com/redshift-downloads/drivers/jdbc/1.2.41.1065/RedshiftJDBC42-no-awssdk-1.2.41.1065.jar) ## Connector Capabilities #### The connector capabilities are shown below: **Crawling** Please see this article [Crawling Data](https://support.ovaledge.com/step-by-step-guide-to-setup-ovaledge-crawlers) for more details on crawling. Supported objects and data types for Crawling are: | **Supported Objects** | **Supported Data Types** | | ---------------------------- | -------------------------------------------------------------- | | Tables, Table Columns, Views | TINYINT, SMALLINT, INT, BIGINT, VARCHAR, CHAR, Timestamp, DATE | **Profiling** Please see [Profiling Data](https://support.ovaledge.com/step-by-step-guide-to-setup-ovaledge-profiling) for more details on profiling. | **Feature** | **Support** | **Remarks** | | ---------------- | --------------------------------------------- | ------------------------------------------------- | | Table Profiling | Row count, Columns count, View sample data | | | View Profiling | Row count, Columns count, View sample data | View is treated as a table for profiling purposes | | Column Profiling | Min, Max, Null count, distinct, top 50 values | | | Full Profiling | Supported | | | Sample Profiling | Supported | | **Lineage Building** | **Lineage Entities** | **Details** | | -------------------- | ----------------------------------------------- | | Table lineage | Supported | | Column lineage | Supported | | Lineage Sources | Stored procedures, functions, views, query logs | **Querying** | **Operation** | **Details** | | ---------------------- | -------------------------- | | Select | Supported | | Insert | Not supported, by default. | | Update | Not supported, by default. | | Delete | Not supported, by default. | | Joins within database | Supported | | Joins outside database | Not supported | | Aggregations | Supported | | Group By | Supported | | Order By | Supported | > By default the service account provided for the connector will be used for any query operations. If the service account has write privileges, then Insert / Update / Delete queries can be executed. #### **Pre-requisites** To use the connector, the following need to be available: * Connection details as specified in the following section should be available. * Service account with read privileges. * JDBC driver is provided by default. In case it needs to be changed, add Qubole Hive client drivers into the OvalEdge Jar path to communicate to the Qubole Hive database. Check the [Configuration section](https://support.ovaledge.com/configuration) for further details on how to add the drivers to the jar path. #### **Connection Details** The following connection settings should be added for connecting to a Qubole Hive database: * **Database Type:** Qubole Hive * **License Type:** Standard * **Connection Name:** Select a Connection name for the Qubole Hive database. The name that you specify is a reference name to easily identify your Qubole Hive database connection in OvalEdge. Example: Qubole Hive Connection1 * **Qubole Endpoint:** Qubole endpoint * **Cluster Label:** Name of the database to connect. * **Driver:** com.qubole.jdbc.jdbc41.core.QDriver * **API Token:** Qubole API Token * **Connection String:** Qubole Hive connection string. Set the Connection string toggle button to automatic, to get the details automatically from the credentials provided. Alternatively, you can manually enter the string.\ **Format:**jdbc:qubole://hive/{clusterLabel}?endpoint={server}\ Example:jdbc:qubole://hive/default?endpoint= > Once connectivity is established, additional configurations for [Crawling](https://support.ovaledge.com/understanding-crawler-settings) and [Profiling](https://support.ovaledge.com/understanding-profiling-settings) can be specified. | **Property** | **Details** | | -------------------------- | ---------------------------------------------------------------------------------- | | **Crawler configurations** | | | Tables, views columns | By default it is selected true | | Crawler rules | Default include tables regex has regex = (.\*) , which can crawl all the tables | | **Profile Settings** | | | Tables and columns | By default it is selected true | | Views and columns | By default it is selected true | | Profile Rules | Default include tables regex has regex = (.\*) , which can profile all the tables | *** Copyright © 2025, OvalEdge LLC, Peachtree Corners GA USA --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ovaledge.com/connectors/connector-repositories/big-data-platform/qubole-hive.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.