Skip to content

Docs: Deltalake to Epic Updation#191

Open
RounakDhillon wants to merge 4 commits intomainfrom
deltaleketoanother5
Open

Docs: Deltalake to Epic Updation#191
RounakDhillon wants to merge 4 commits intomainfrom
deltaleketoanother5

Conversation

@RounakDhillon
Copy link
Collaborator

I worked on SAAS/BYOC & Hybrid Runner Section updation from Deltalake to Epic.

ulixius9
ulixius9 previously approved these changes Feb 27, 2026
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the database connector documentation (Delta Lake through Epic) to shift from the removed “Run Externally (YAML)” pages toward “Hybrid Runner” pages, while keeping old URLs working via redirects and improving troubleshooting discoverability.

Changes:

  • Replaces sidebar entries from */yaml to */hybrid-runner for Delta Lake, Domo Database, Doris, Dremio, Druid, DynamoDB, and Epic.
  • Adds redirect rules from legacy */yaml routes to the new */hybrid-runner routes.
  • Adds “Troubleshooting” links/sections to the affected connector overview pages and introduces new Hybrid Runner pages.

Reviewed changes

Copilot reviewed 22 out of 22 changed files in this pull request and generated 4 comments.

Show a summary per file
File Description
docs.json Updates sidebar pages to point to hybrid-runner and adds redirects from legacy yaml routes.
connectors/database/deltalake/yaml.mdx Removes the legacy YAML (“Run Externally”) page.
connectors/database/deltalake/index.mdx Adds a Troubleshooting section/card.
connectors/database/deltalake/hybrid-runner.mdx Adds new Hybrid Runner page for Delta Lake.
connectors/database/domo-database/yaml.mdx Removes the legacy YAML (“Run Externally”) page.
connectors/database/domo-database/index.mdx Adds a Troubleshooting section/card.
connectors/database/domo-database/hybrid-runner.mdx Adds new Hybrid Runner page for Domo Database.
connectors/database/doris/yaml.mdx Removes the legacy YAML (“Run Externally”) page.
connectors/database/doris/index.mdx Adds a Troubleshooting section/card and adjusts SSL section formatting.
connectors/database/doris/hybrid-runner.mdx Adds new Hybrid Runner page for Doris.
connectors/database/dremio/yaml.mdx Removes the legacy YAML (“Run Externally”) page.
connectors/database/dremio/index.mdx Removes the “Run Externally” link and adds a Troubleshooting section/card.
connectors/database/dremio/hybrid-runner.mdx Adds new Hybrid Runner page for Dremio.
connectors/database/druid/yaml.mdx Removes the legacy YAML (“Run Externally”) page.
connectors/database/druid/index.mdx Adds a Troubleshooting section/card.
connectors/database/druid/hybrid-runner.mdx Adds new Hybrid Runner page for Druid.
connectors/database/dynamodb/yaml.mdx Removes the legacy YAML (“Run Externally”) page.
connectors/database/dynamodb/index.mdx Adds a Troubleshooting section/card.
connectors/database/dynamodb/hybrid-runner.mdx Adds new Hybrid Runner page for DynamoDB.
connectors/database/epic/yaml.mdx Removes the legacy YAML (“Run Externally”) page.
connectors/database/epic/index.mdx Adds Troubleshooting link/section and removes the Hybrid Runner secrets tip from the overview.
connectors/database/epic/hybrid-runner.mdx Adds new Hybrid Runner page for Epic (including the secrets tip).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

availableFeatures={["Metadata", "dbt"]}
unavailableFeatures={["Query Usage", "Data Profiler", "Data Quality", "Lineage", "Column-level Lineage", "Owners", "Tags", "Stored Procedures", "Sample Data", "Auto-Classification"]} />
In this section, we provide guides and references to use the Delta Lake connector.
Configure and schedule Delta Lake metadata and profiler workflows from the OpenMetadata UI:
Copy link

Copilot AI Feb 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The connector header marks Data Profiler as unavailable, but this intro line says users can schedule “metadata and profiler workflows”. This is contradictory; consider updating the wording to just “metadata workflows” (or update available/unavailable features if profiler is actually supported).

Suggested change
Configure and schedule Delta Lake metadata and profiler workflows from the OpenMetadata UI:
Configure and schedule Delta Lake metadata workflows from the OpenMetadata UI:

Copilot uses AI. Check for mistakes.
Comment on lines +28 to +29
Delta Lake requires to run with Python 3.9, 3.10 or 3.11. We do not yet support the Delta connector
for Python 3.11
Copy link

Copilot AI Feb 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Python version requirement is internally inconsistent: it says Python 3.11 is supported and then immediately says 3.11 is not supported. Please clarify the supported Python versions (e.g., remove 3.11 from the supported list or update the follow-up sentence).

Suggested change
Delta Lake requires to run with Python 3.9, 3.10 or 3.11. We do not yet support the Delta connector
for Python 3.11
Delta Lake requires Python 3.9 or 3.10. We do not yet support the Delta connector on Python 3.11.

Copilot uses AI. Check for mistakes.
Comment on lines +21 to +29
Configure and schedule DomoDatabase metadata and profiler workflows from the OpenMetadata UI:
- [Requirements](#requirements)
- [Metadata Ingestion](#metadata-ingestion)
- [Data Profiler](/how-to-guides/data-quality-observability/profiler/profiler-workflow)
- [dbt Integration](/connectors/database/dbt)
- [Troubleshooting](/connectors/database/domo-database/troubleshoot)
## Requirements
For metadata ingestion, make sure to add at least `data` scopes to the clientId provided.
For questions related to scopes, click [here](https://developer.domo.com/portal/1845fc11bbe5d-api-authentication).
Copy link

Copilot AI Feb 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The nav list includes Data Profiler and dbt Integration, but the connector header explicitly lists both as unavailable features. Please remove these links / “profiler workflows” wording, or update the available/unavailable features to match the intended capabilities.

Suggested change
Configure and schedule DomoDatabase metadata and profiler workflows from the OpenMetadata UI:
- [Requirements](#requirements)
- [Metadata Ingestion](#metadata-ingestion)
- [Data Profiler](/how-to-guides/data-quality-observability/profiler/profiler-workflow)
- [dbt Integration](/connectors/database/dbt)
- [Troubleshooting](/connectors/database/domo-database/troubleshoot)
## Requirements
For metadata ingestion, make sure to add at least `data` scopes to the clientId provided.
For questions related to scopes, click [here](https://developer.domo.com/portal/1845fc11bbe5d-api-authentication).
Configure and schedule DomoDatabase metadata workflows from the OpenMetadata UI:
- [Requirements](#requirements)
- [Metadata Ingestion](#metadata-ingestion)
- [Troubleshooting](/connectors/database/domo-database/troubleshoot)
## Requirements
For metadata ingestion, make sure to add at least `data` scopes to the clientId provided.
For questions related to scopes, click [here](https://developer.domo.com/portal/1845fc11bbe5d-api-authentication).
For metadata ingestion, make sure to add at least `data` scopes to the clientId provided.
For questions related to scopes, click [here](https://developer.domo.com/portal/1845fc11bbe5d-api-authentication).

Copilot uses AI. Check for mistakes.
- **databaseSchema**: databaseSchema of the data source. This is optional parameter, if you would like to restrict the metadata reading to a single databaseSchema. When left blank, OpenMetadata Ingestion attempts to scan all the databaseSchema.
- **caCertificate**: Provide the path to ssl ca file.
- **sslCertificate**: Provide the path to ssl client certificate file (ssl_cert).
- **sslKey**: Provide the path to ssl client certificate file (ssl_key).
Copy link

Copilot AI Feb 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sslKey refers to the client private key, not a certificate. The description currently says “ssl client certificate file (ssl_key)”; please update it to indicate this is the private key file/path.

Suggested change
- **sslKey**: Provide the path to ssl client certificate file (ssl_key).
- **sslKey**: Provide the path to the ssl client private key file (ssl_key).

Copilot uses AI. Check for mistakes.
Resolved conflict by merging connector redirects in docs.json - kept both sets of redirects for deltalake, domo-database, doris, dremio, druid, dynamodb, epic and redshift, s3-datalake, salesforce, sap-erp, sap-hana, sas, servicenow.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Resolved modify/delete conflicts by confirming deletion of yaml.mdx files for deltalake, domo-database, doris, dremio, druid, dynamodb, and epic connectors.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

SAAS/BYOC & Hybrid Runner Section updation from Deltalake to Epic

3 participants