dr_publish_metadata()

Catalog adapters receive product metadata after execution according to their declared lifecycle support. A function is sufficient for a small integration. Its return value is ignored. Metadata delivery is separate from data publication: a catalog failure is recorded as a warning and does not pretend that a committed data release was undone.

Usage

dr_publish_metadata(catalog, metadata, ...)

Arguments

catalog: Function or catalog adapter.
metadata: Descriptive product run metadata without input rows or connections, or a dr_dbt_result for a catalog supporting dbt artifacts.
...: Reserved for adapter-specific options.

Value

The adapter's result; no specific value is required. Functions are called invisibly. The OpenMetadata dbt adapter returns a delivery receipt.

Details

dataraft.dbt::dr_dbt_build() and dataraft.dbt::dr_dbt_test() also accept a catalog function, or an S3 adapter with dr_capabilities(x)$metadata_inputs = "dr_dbt_result". These receive the full dbt result, including local artifact paths, the manifest, and dbt stdout/stderr. Callback authors control what is transmitted; these diagnostics can contain SQL or database messages. Valid artifacts from failed dbt tests can still be delivered without changing the dbt outcome. dataraft.adapters::dr_catalog_openmetadata_dbt() delegates to the existing OpenMetadata ingestion engine and returns a retryable, credential-free delivery receipt.

Examples

received <- NULL
dr_publish_metadata(function(metadata) received <<- metadata,
  list(product = "orders", rows = 2L))

Documentation source snapshot · View source at d9cb454 ↗
Code examples are documented source examples; they are not executed in this website build.