Skip to main content

​
Troubleshooting

​
Workflow Deployment Error

If there were any errors during the workflow deployment process, the Ingestion Pipeline Entity will still be created, but no workflow will be present in the Ingestion container.
  • You can then Edit the Ingestion Pipeline and Deploy it again.
  • From the Connection tab, you can also Edit the Service if needed.

​
Connector Debug Troubleshooting

This section provides instructions to help resolve common issues encountered during connector setup and metadata ingestion in OpenMetadata. Below are some of the most frequently observed troubleshooting scenarios.

​
How to Enable Debug Logging for Any Ingestion

To enable debug logging for any ingestion workflow in OpenMetadata:
  1. Navigate to Services Go to Settings > Services > Service Type (e.g., Database) in the OpenMetadata UI.
  2. Select a Service Choose the specific service for which you want to enable debug logging.
  3. Access Agents Tab Go to the Agents tab and click the three-dot menu on the right-hand side of the ingestion type, and select Edit.
  4. Enable Debug Logging In the configuration dialog, enable the Debug Log option and click Next.
  5. Schedule and Submit Configure the schedule if needed and click Submit to apply the changes.

​
Permission Issues

If you encounter permission-related errors during connector setup or metadata ingestion, ensure that all the prerequisites and access configurations specified for each connector are properly implemented. Refer to the connector-specific documentation to verify the required permissions.

​
ClickZetta-Specific Issues

The following issues are specific to the ClickZetta connector.

​
Connection Fails with a Missing Virtual Cluster

ClickZetta runs queries through a virtual cluster, so the Virtual Cluster field is required. If the connection test fails, confirm the virtual cluster name is correct and that the connecting user’s role has USAGE on it. Run the following grant:

​
No Usage or Lineage Is Produced

Query Usage and query-based lineage read from a ClickZetta query-history source. Set Query History Table to information_schema.job_history for workspace-local history or sys.information_schema.job_history for cross-workspace history. Confirm that the user has SELECT on the selected source. A custom table or view must expose these columns:
  • Query columns: query_text, query_type, user_name
  • Scope and timing columns: database_name, schema_name, start_time, end_time, duration, aborted, cost
The history is scoped to the configured workspace and schema, so a mismatched Workspace or Database Schema can return no rows.

​
No Schemas or Tables Are Ingested

Leave Database Schema blank to scan all schemas, or set it to restrict ingestion to a single schema. Confirm the connecting role has SELECT on the schemas you expect to ingest, and review your filter patterns in the What to Ingest step.