Skip to content

Skip schema validation of the dbt_model dataset facet - #337

Draft
tnazarew wants to merge 1 commit into
mainfrom
dbt/skip-dbt-model-facet-schema
Draft

tnazarew wants to merge 1 commit into
mainfrom
dbt/skip-dbt-model-facet-schema

Conversation

@tnazarew

Copy link
Copy Markdown
Collaborator

Problem

dbt syntax validation fails on recent openlineage-dbt releases with facet type dbt_model not recognized.

openlineage-dbt has emitted the dbt_model dataset facet (DbtModelDatasetFacet) since about 1.47, with _schemaURL …/integration/common/openlineage/schema/dbt-model-dataset-facet.json. That schema file doesn't exist at any OpenLineage tag or on main: the facet is defined only in integration/common/src/openlineage/common/provider/dbt/facets.py. The validator has no schema to load, so the facet is reported as unrecognized.

Change

Add dbt-model-dataset to the list of common facets whose schema validation is skipped, next to dbt-version-run and dbt-run-run. This should be reverted once upstream publishes the schema.

Verification

Full dbt validation of the 1.54 events from CI run 38702151241 passes 23/23 with this change.

Note

#257 rewrites the same is_custom_facet function and validates dbt-run and dbt-version against their schemas instead of skipping them. Whichever PR merges second needs to keep dbt_model skipped, because it has no schema upstream.

🤖 Generated with Claude Code

openlineage-dbt emits dbt_model (DbtModelDatasetFacet) with _schemaURL
.../integration/common/openlineage/schema/dbt-model-dataset-facet.json,
but that file is not published at any OpenLineage tag or on main; the
facet exists only in facets.py. Syntax validation therefore fails with
"facet type dbt_model not recognized". Treat it like dbt_version and
dbt_run until upstream publishes the schema.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: tnazarew <tomasz.nazarewicz@getindata.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.

1 participant