DRDataRaft/ docs
GitHub ↗

backend-protocols()

Provider packages implement these S3 protocols for their own specification and result classes. The core does not import or call provider implementations. Implementations must preserve the write gate, pinned release identity and caller-owned connection lifetime. Unsupported objects fail explicitly.

Usage

dr_connect_backend(x, ...)

dr_close_backend(x, ...)

dr_resolve_release(x, ...)

dr_read_release_data(x, ...)

dr_release_table(x, ...)

dr_as_release_source(x, ...)

dr_land_source(x, ...)

dr_read_release_source(x, ...)

dr_publish_model_result(x, ...)

dr_with_release_backend(x, ...)

dr_read_model_release(x, ...)

dr_registry_data(x, ...)

dr_check_pipeline(x, ...)

dr_diagnostic_measurements(x, ...)

dr_measurement_quality(x, ...)

dr_backend_lineage(x, ...)

dr_as_parquet_source(x, ...)

dr_as_target(x, ...)

dr_filter_metadata(x, ...)

dr_replace_backend_sources(x, ...)

dr_configure_target(x, ...)

Arguments

x
Backend specification, connected backend, source or result.


...
Operation-specific arguments forwarded to the provider method.

Value

The operation's backend result; see the provider documentation.
Documentation source snapshot · View source at d9cb454 ↗
Code examples are documented source examples; they are not executed in this website build.

Search documentation

Search functions, packages and guides.