DRDataRaft/ docs
GitHub ↗

dr_source_release()

Execution resolves an omitted release_id once and records its immutable identity. Pass a configuration to open an existing lake read-only, collect the selected release into an ordinary tibble, and close the owned connection. This requires enough memory for the release. A connected lake instead returns a lazy table and remains caller-owned; keep it open while using that table. Construction and validation do not open or create a lake. This source connects governed releases to ordinary product composition and consumer exports. When publishing back to the same lake, execution can reuse its open handle; configuration sources still return materialized values without owning it.

Usage

dr_source_release(lake, asset, release_id = NULL)

Arguments

lake
Connected lake or dr_lake_config() describing an existing lake.


asset
Published asset name.


release_id
Optional immutable release identifier.

Value

A source adapter. Reads return a lazy table for a connected lake or a tibble for a configuration, with the exact release reference attached.

Examples

if (FALSE) {
  dataraft.core::dr_product("summary") |>
    dataraft.core::dr_add_source(dr_source_release(lake, "orders")) |>
    dataraft.core::dr_add_recipe(dataraft.core::dr_recipe() |> dataraft.core::dr_step_transform(function(data) dplyr::summarise(data, rows = dplyr::n()))) |>
    dataraft.core::dr_run()
}
Documentation source snapshot · View source at 113c179 ↗
Code examples are documented source examples; they are not executed in this website build.

Search documentation

Search functions, packages and guides.