open-metadata
Oracle Connector: schemaDefinition empty for some views (LONG column issue in ALL.VIEWS.text)
Describe the issue
When running the Oracle metadata ingestion pipeline, we noticed that some views are ingested with an *empty schemaDefinition, while others in the same schema are populated correctly . Example:
- "DWH.default.dwh_psb.yudep_accounts schemaDefinition is empty
- Other views in the same schema dhpsb schemaDefinition is present
Additional context
In previous OpenMetadata vecsions, schemalefinition for these views was populated.
- The issue seems celated to Ocacle's ALL_VIEWS.TEXT column (datatype LONG"), which max retuch empty results for certain views. This behavier is inconsistent: some views in the same schema ace ingested correctly, while others are not. Our ingestion pipeline is configured with: schemati teclattern: includes: ["*DWH_PSB$"] use FqnForFiltering: false Despite this some views still come with an empty schemaDefinition.
Why this matters Without a populated schemaDefinition, we cannot use lineage and documentation features effectively in OpenMetadata for affected views. Expected behavior The Oracle connector should consistently populate schemaDefinition for all views, ideally by using DBMS_METADATA. GET DDL instead of ALL_VIEWS. TEXT for better reliability. Environment • OpenMetadata version: 1.9.7 • Database: Oracle • Service: DWH Suggested solution • Switch the Oracle connector implementation to use DBMS METADATA-GET DDL for views (instead of ALL_VIEWS. TEXT) • Or provide a configuration option to choose between ALL VIEWS- TEXT and DEMS_METADATA GET DDI- References • Related issue: #14238 (Support for getting Oracle view definitions filtered by schema)
We are running into the same problem, whilst evaluating Open-Metadata for us. The empty "View Definition" is a major hinderence for us.
We are running into the same problem, whilst evaluating Open-Metadata for us. The empty "View Definition" is a major hinderence for us.
I solved the problem by changing the connector script.