[WIP][dagster-airbyte] RFC: Prototype airbyte_assets
asset decorator
#22847
+304
−86
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary & Motivation
Current state
Currently, users can create their Airbyte assets in three different ways in Dagster.
load_assets_from_airbyte_instance
CacheableAssetsDefinition
load_assets_from_airbyte_project
CacheableAssetsDefinition
build_airbyte_assets
CacheableAssetsDefinition
, but multi-assetLooks like this, assuming no overlap in Airbyte connection between approaches:
Propositions
build_airbyte_assets
in an asset decorator,airbyte_assets
, to allow more flexibility with the resource.In this approach we would keep
load_assets_from_airbyte_instance
andload_assets_from_airbyte_project
as-is.In this approach we would keep
load_assets_from_airbyte_instance
andload_assets_from_airbyte_project
as-is.Todo
load_assets_from_airbyte_instance
andload_assets_from_airbyte_project
How I Tested These Changes
TODO