> 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/release8.2/connectors/connector-repositories/rdbms/dremio.md).

# Dremio

This article outlines the integration with the Dremio connector, enabling streamlined metadata management through features such as crawling, profiling, querying, data preview, data quality, and lineage building (both automatic and manual).

This connector supports connectivity to Dremio environments using Traditional Jar and Arrow Flight JDBC drivers, providing flexibility based on deployment and performance requirements. It supports metadata extraction for schemas, tables, views, and columns.

<div align="left"><img src="/files/DWnvLwiiSbsTrL1kxQ1G" alt="" height="307" width="624"></div>

### Overview

#### Connector Details

| Connector Category                                                         | RDBMS                  |
| -------------------------------------------------------------------------- | ---------------------- |
| OvalEdge Release Supported                                                 | Release6.3.4 and later |
| <p>Connectivity</p><p>\[How the connection is established with Dremio]</p> | JDBC driver            |
| Verified Dremio Version                                                    | Dremio 26.x            |

{% hint style="info" %}
The Dremio connector has been validated with the mentioned "Verified Dremio Version" and is expected to be compatible with other supported Dremio versions. If there are any issues with validation or metadata crawling, please submit a support ticket for investigation and feedback.
{% endhint %}

#### Connector Features

| Feature                                      | Availability |
| -------------------------------------------- | :----------: |
| Crawling                                     |       ✅      |
| Delta Crawling                               |       ❌      |
| Profiling                                    |       ✅      |
| Sample Profiling                             |       ✅      |
| Query Sheet                                  |       ✅      |
| Data Preview                                 |       ✅      |
| Auto Lineage                                 |       ✅      |
| Manual Lineage                               |       ✅      |
| Secure Authentication via Credential Manager |       ✅      |
| Data Quality                                 |       ✅      |
| DAM (Data Access Management)                 |       ❌      |
| Bridge                                       |       ✅      |

#### Metadata Mapping

The following objects are crawled from Dremio and mapped to the corresponding UI assets.

<table><thead><tr><th width="179.5999755859375">Dremio Object</th><th width="156.4000244140625">Dremio Attribute</th><th width="169.199951171875">OvalEdge Attribute</th><th width="172">OvalEdge Category</th><th width="148">OvalEdge Type</th></tr></thead><tbody><tr><td>Schema</td><td>SCHEMA_NAME</td><td>Schema</td><td>Schemas</td><td>-<br></td></tr><tr><td>Table</td><td>TABLE_NAME</td><td>Table</td><td>Tables</td><td>Table</td></tr><tr><td>TABLE_TYPE</td><td>Table</td><td>Tables</td><td>Table</td><td>-</td></tr><tr><td>Columns</td><td>COLUMN_NAME</td><td>Column</td><td>Table Columns</td><td>-</td></tr><tr><td>DATA_TYPE</td><td>Column Type</td><td>Table Columns</td><td>-</td><td>-</td></tr><tr><td>ORDINAL_POSITION</td><td>Column Position</td><td>Table Columns</td><td>-</td><td>-</td></tr><tr><td>COLUMN_SIZE</td><td>Data Type Size</td><td>Table Columns</td><td>-</td><td>-</td></tr><tr><td>Views</td><td>TABLE_NAME</td><td>View Name</td><td>Tables</td><td>View</td></tr><tr><td>VIEW_DEFINITION</td><td>View Query</td><td>Views</td><td>View</td><td>-</td></tr></tbody></table>

### Set up a Connection

#### Prerequisites

The following are the prerequisites to establish a connection:

**Whitelisting Ports**

Ensure that the required inbound ports are whitelisted to allow OvalEdge to establish a connection with the Dremio server. For connections using the Traditional JDBC Driver, the default port 31010 must be accessible, while connections using the Arrow Flight JDBC Driver default port 32010 to be accessible.

{% hint style="info" %}
If custom ports are configured in Dremio, ensure that the updated port numbers are specified during connection setup, the corresponding ports are whitelisted, and communication between the OvalEdge application and Dremio server is properly established.
{% endhint %}

**External Supporting Files**

{% hint style="warning" %}
The required external JAR files are included as part of the OvalEdge installation artifacts. For driver installation and configuration details, refer to the [Connector Drivers Setup Guide](https://docs.ovaledge.com/connectors/additional-requirements/connector-drivers-setup-guide). Please contact the OvalEdge Team for assistance related to the driver files and configuration setup.
{% endhint %}

| File Name                         | Description                                                                                          |
| --------------------------------- | ---------------------------------------------------------------------------------------------------- |
| flight-sql-jdbc-driver-10.0.0.jar | For Dremio versions earlier than 21.x, use the JDBC Driver version 10.0.0 to establish connectivity. |

**Service Account User Permissions**

{% hint style="info" %}
It is recommended to use a separate service account to establish the connection to the data source, configured with the following minimum set of permissions.
{% endhint %}

{% hint style="warning" %}
👨‍💻 Who can provide these permissions? These permissions are typically granted by the Dremio administrator, as users may not have the required access to assign them independently.
{% endhint %}

| Operation                     | Objects                          | System Tables                | Access Permission                                   |
| ----------------------------- | -------------------------------- | ---------------------------- | --------------------------------------------------- |
| Crawling                      | Schema                           | INFORMATION\_SCHEMA.SCHEMATA | SELECT                                              |
| Crawling                      | Tables                           | INFORMATION\_SCHEMA.TABLES   | SELECT                                              |
| Crawling                      | Table Columns                    | INFORMATION\_SCHEMA.COLUMNS  | SELECT                                              |
| Crawling & Lineage Building   | Views                            | INFORMATION\_SCHEMA.VIEWS    | SELECT                                              |
| Profiling                     | Row Count                        | User Data Tables             | SELECT                                              |
| Profiling                     | Data Profiling                   | User Data Tables             | SELECT                                              |
| Profiling                     | Sample Data                      | User Data Tables             | SELECT                                              |
| Profiling                     | Column Statistics                | User Data Tables             | SELECT                                              |
| Crawling                      | Column Matching                  | User Data Tables             | SELECT                                              |
| Query Logging                 | Query Logs                       | NAS.queries.json             | SELECT                                              |
| Data Access & Governance      | Governed Data Query Execution    | User Data Tables             | SELECT                                              |
| Data Access & Query Execution | Data Query Execution (Async)     | User Data Tables             | SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER, DROP |
| Data Access & Query Execution | Data Query Execution (Real-Time) | User Data Tables             | SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER, DROP |
| Connection Validation         | <p>-<br></p>                     | INFORMATION\_SCHEMA.VIEWS    | SELECT                                              |

#### Connection Configuration Steps

{% hint style="warning" %}
Users are required to have the Connector Creator role in order to configure a new connection.
{% endhint %}

1. Log into OvalEdge, go to **Administration > Connectors**, click **+ (New Connector)**, search for **Dremio**, and complete the required parameters.

{% hint style="info" %}
Fields marked with an asterisk (\*) are mandatory for establishing a connection.
{% endhint %}

<table><thead><tr><th width="229.4000244140625">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Connector Type</td><td>By default, "Dremio" is displayed as the selected connector type.</td></tr><tr><td>Credential Manager*</td><td><p>Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on your selection.</p><p>Supported Credential Managers:</p><ul><li>OE Credential Manager</li><li>AWS Secrets Manager</li><li>HashiCorp Vault</li><li>Azure Key Vault</li></ul><p>For more details, click<a href="https://docs.ovaledge.com/connectors/additional-requirements/credential-manager-configuration"> here</a>. </p></td></tr><tr><td>License Add Ons</td><td><ul><li>Select the checkbox for Auto Lineage Add-On to build data lineage automatically.</li><li>Select the checkbox for Data Quality Add-On to identify data quality issues using data quality rules and anomaly detection.</li></ul><p>For more details, click<a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/license-types-and-add-ons"> here</a>. </p></td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the Dremio connection              </p><p>(Example: "Dremio").</p></td></tr><tr><td>Connector Environment</td><td><p>Select the environment (Example: PROD, STG) configured for the connector.</p><p>For more details, click<a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/prerequisites#connector-environment"> here</a>. </p></td></tr><tr><td>JDBC Driver*</td><td><p>Select the JDBC driver type to connect to Dremio:</p><ul><li>Traditional Jar – Uses the standard Dremio JDBC connection.</li><li>Arrow Flight – Uses Apache Arrow Flight Dremio for high-performance data transfer.</li></ul></td></tr><tr><td>Connector description</td><td>Enter a brief description of the connector.</td></tr><tr><td>Server*</td><td><p>Enter the Dremio database server name or IP address </p><p><strong>Example:</strong></p><ul><li>dremio.*****ny.com</li><li>192.168.1.100</li></ul></td></tr><tr><td>Port*</td><td><p>By default, the port number for the Dremio, "31010" is auto-populated for Traditional Jar. If required, the port number can be modified as per the custom port number that is configured for your Dremio.</p><p><strong>Note:</strong> If you are using the Arrow Flight JDBC Driver, ensure that the inbound port 32010 by default is also whitelisted.</p></td></tr><tr><td>Disable Certificate Verification*</td><td>Select True to bypass SSL certificate validation during connection. Select False to enforce certificate verification for secure communication.</td></tr><tr><td>Is SSL Enabled*</td><td>Select True to enable SSL/TLS encryption for the connection. Select False to connect without SSL encryption. </td></tr><tr><td>Driver*</td><td>By default, the Dremio driver details are auto-populated. </td></tr><tr><td>Username*</td><td>Enter the service account username set up to access the Dremio database (Example: "oesauser").</td></tr><tr><td>Password*</td><td>Enter the password associated with the service account user.</td></tr><tr><td>Connection String</td><td><p>Configure the connection string for the Dremio database:</p><ul><li>Automatic Mode: The system generates a connection string based on the provided credentials.</li><li>Manual Mode: Enter a valid connection string manually.</li></ul><p>Replace placeholders with actual database details.</p><p>{sid} refers to Database Name.</p></td></tr><tr><td>Plugin Server</td><td>Enter the server’s name when running as a plugin server.</td></tr><tr><td>Plugin Port</td><td>Enter the port number on which the plugin is running.</td></tr></tbody></table>

<table data-header-hidden><thead><tr><th width="230.2000732421875"></th><th></th></tr></thead><tbody><tr><td><strong>Default Governance Roles</strong></td><td></td></tr><tr><td>Default Governance Roles*</td><td>Select the appropriate users or teams for each governance role from the drop-down list. All users and teams configured in OvalEdge Security are displayed for selection.</td></tr><tr><td><strong>Admin Roles</strong></td><td></td></tr><tr><td>Admin Roles*</td><td>Select one or more users from the dropdown list for Integration Admin and Security &#x26; Governance Admin. All users configured in OvalEdge Security are available for selection.</td></tr><tr><td><strong>No of Archive Objects</strong></td><td></td></tr><tr><td>No Of Archive Objects*</td><td><p>This shows the number of recent metadata changes to a dataset at the source. By default, it is off. To enable it, toggle the Archive button and specify the number of objects to archive.</p><p>Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.</p></td></tr><tr><td><strong>Bridge</strong></td><td></td></tr><tr><td>Select Bridge*</td><td><p>If applicable, select the bridge from the drop-down list.</p><p>The drop-down list displays all active bridges configured in OvalEdge. These bridges enable communication between data sources and OvalEdge without altering firewall rules.</p></td></tr></tbody></table>

2. After entering all connection details, the following actions can be performed:
   * Click **Validate** to verify the connection.
   * Click **Save** to store the connection for future use.
   * Click **Save & Configure** to apply additional settings before saving.
3. The saved connection will appear on the Connectors home page.

### Manage Connector Operations

#### Crawl/Profile

{% hint style="info" %}
To perform crawl and profile operations, users must be assigned the Integration Admin role.
{% endhint %}

The **Crawl/Profile** button allows users to select one or more schemas for crawling and profiling.&#x20;

1. Navigate to the **Connectors** page and click **Crawl/Profile**.
2. Select the **schemas** to **crawl**.
3. The **Crawl** option is selected by default. Click the **Crawl & Profile** radio button to run both operations.
4. Click **Run** to collect metadata from the connected source and load it into the OvalEdge **Data Catalog**.
5. After a successful **crawl**, the information appears in the **Data Catalog > Databases tab**.

The **Schedule** checkbox allows automated crawling and profiling at defined intervals, from a minute to a year.

1. Click the **Schedule** checkbox to enable the Select **Period drop-down**.
2. Select a **time period** for the operation from the drop-down menu.
3. Click **Schedule** to initiate metadata collection from the connected source.
4. The system will automatically execute the selected operation (**Crawl or Crawl & Profile**) at the scheduled time.

#### Other Operations

The Connectors page in the OvalEdge provides a centralized view of all configured connectors, including their health status.

**Managing connectors includes:**

* **Connectors Health:** Displays the current status of each connector using a green icon for active connections and a red icon for inactive connections, helping to monitor the connectivity with data sources.
* **Viewing:** Click the Eye icon next to the connector name to view connector details.

**Nine Dots Menu Options:**

To view, edit, validate, build lineage, configure, or delete connectors, click on the Nine Dots menu.

* **Edit Connector:** Update and revalidate the data source.
* **Validate Connector:** Check the connection's integrity.
* **Settings:** Modify connector settings.
  * **Crawler:** Configure data extraction.
  * **Profiler:** Customize data profiling rules and methods.
  * **Access Instructions:** Add notes on how data can be accessed.
  * **Query Policies:** Define query execution rules based on roles.
  * **Business Glossary Settings:** Manage term associations at the connector level.
  * **Anomaly Detection Settings:** Configure anomaly detection preferences at the connector level.
  * **Others:** Configure notification recipients for metadata changes.
* **Build Lineage:** Automatically build data lineage from source code.
* **Delete Connector:** Remove a connector with confirmation.

For more details on connector settings, click[ here](https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/connector-settings).&#x20;

#### Connectivity Troubleshooting

If incorrect parameters are entered, error messages may appear. Ensure all inputs are accurate to resolve these issues. If issues persist, contact the assigned support team.

<table><thead><tr><th width="85.60003662109375">S.No.</th><th width="229.5999755859375">Error Message(s)</th><th>Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td>1</td><td><p>Connection refused</p><p>Connection timeout</p></td><td><p><strong>Error Description:</strong></p><p>The OvalEdge application cannot establish a network connection to the Dremio server.</p><p></p><p><strong>Resolution:</strong></p><ul><li>Verify that the server hostname or IP address is correct.</li><li>Ensure the correct port is configured (Arrow Flight: 32010, Traditional JDBC: 31010).</li><li>Confirm that the Dremio server is running and reachable.</li><li>Verify that firewall rules allow communication through the configured port.</li><li>Test connectivity using telnet &#x3C;server> &#x3C;port>.</li><li>Ensure the connection string matches the selected driver type.</li><li>Verify SSL settings if SSL is enabled.</li></ul></td></tr><tr><td>2</td><td><p><br></p><p>Failed to retrieve DataSource from DataSourceProvider</p></td><td><p><strong>Error Description:</strong></p><p>The connection pool could not initialize the Dremio data source.</p><p></p><p><strong>Resolution:</strong></p><ul><li>Verify the correct JDBC driver class is configured:</li><li>Ensure the JDBC driver JAR is available in the OvalEdge classpath.</li><li>Verify the connection string format.</li><li>Confirm network and SSL settings are valid.</li><li>Recreate the connection if cached connection details are causing issues.</li><li>Verify that the driver version is compatible with the Dremio server version.</li></ul></td></tr><tr><td>3</td><td><p>SSL connection failed</p><p>Certificate validation error</p></td><td><p><strong>Error Description:</strong></p><p>The SSL connection could not be established due to certificate validation issues or incorrect SSL configuration.</p><p></p><p><strong>Resolution:</strong></p><ul><li>Verify that Is SSL Enabled matches the Dremio server configuration.</li><li>Configure Disable Certificate Verification appropriately.</li><li>Ensure SSL certificates are valid and trusted.</li><li>Verify the SSL parameters in the JDBC connection string.</li><li>If using self-signed certificates, enable certificate verification bypass only if permitted by your security policies.</li></ul></td></tr><tr><td>4</td><td>validateConnection() failed</td><td><p><strong>Error Description:</strong></p><p>Connection validation failed even though the connection credentials are correct.</p><p></p><p><strong>Resolution:</strong></p><ul><li>Verify that the user has access to the INFORMATION_SCHEMA views.</li><li>Ensure the JDBC driver is installed and loaded correctly.</li><li>Confirm that network connectivity and SSL settings are working.</li><li>Verify that the validation query can be executed directly in Dremio.</li><li>Review OvalEdge and Dremio logs for detailed error information.</li></ul></td></tr><tr><td>5</td><td><p>No schemas returned</p><p>getRemoteDatabases() failed </p></td><td><p><strong>Error Description:</strong></p><p>OvalEdge cannot retrieve schema information from Dremio.</p><p></p><p><strong>Resolution:</strong></p><ul><li>Verify that the user has access to INFORMATION_SCHEMA.SCHEMATA.</li><li>Ensure the Dremio environment contains accessible schemas.</li><li>Confirm that the service account has sufficient permissions.</li><li>Review logs for SQL or permission-related errors.</li><li>Validate schema access directly from Dremio.</li></ul></td></tr><tr><td>6</td><td>Unable to connect after changing JDBC driver type</td><td><p><strong>Error Description:</strong></p><p>The configured driver type does not match the Dremio server version or connection settings.</p><p></p><p><strong>Resolution:</strong></p><ul><li>Use Arrow Flight JDBC Driver for Dremio version 21.x and later.</li><li>Use Traditional JDBC Driver for older Dremio versions if required.</li><li>Verify that the corresponding port is configured correctly.</li><li>Ensure the connection string format matches the selected driver type.</li><li>Recreate the connection if the driver type was changed after setup.</li></ul></td></tr><tr><td>7</td><td>Connection failed due to incorrect port configuration</td><td><p><strong>Error Description:</strong></p><p>The configured port does not match the Dremio service endpoint.</p><p></p><p><strong>Resolution:</strong></p><ul><li>Arrow Flight JDBC Driver: 32010.</li><li>Traditional JDBC Driver: 31010.</li><li>Verify that any custom port configured in Dremio is also configured in OvalEdge.</li><li>Test connectivity using telnet or another network utility.</li><li>Ensure firewall rules allow access to the configured port.</li></ul></td></tr></tbody></table>

***

&#x20;Copyright © 2026, 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/release8.2/connectors/connector-repositories/rdbms/dremio.md?ask=<question>&goal=<endgoal>
```

`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.