Dagster allows you to represent your Looker project as assets, alongside other your other technologies like dbt and Sling. This allows you to see how your Looker assets are connected to your other data assets, and how changes to other data assets might impact your Looker project.
( experimental ) This API may break in future versions, even between dot releases.
A decorator for defining Looker assets in a project.
project_dir (Path) – The path to the Looker project directory.
Examples
from pathlib import Path
from dagster_looker import looker_assets
@looker_assets(project_dir=Path("my_looker_project"))
def my_looker_project_assets(): ...
( experimental ) This API may break in future versions, even between dot releases.
Holds a set of methods that derive Dagster asset definition metadata given a representation of a LookML element (dashboards, explores, views).
This class is exposed so that methods can be overriden to customize how Dagster asset metadata is derived.
A method that takes in a dictionary representing a LookML element (dashboards, explores, views) and returns the Dagster asset key that represents the element.
The LookML element is parsed using lkml. You can learn more about this here:
https://lkml.readthedocs.io/en/latest/simple.html.
You can learn more about LookML dashboards and the properties available in this dictionary here: https://cloud.google.com/looker/docs/reference/param-lookml-dashboard.
You can learn more about LookML explores and views and the properties available in this dictionary here: https://cloud.google.com/looker/docs/reference/lookml-quick-reference.
This method can be overriden to provide a custom asset key for a LookML element.
lookml_element (Tuple[Path, Mapping[str, Any]]) – A tuple with the path to file defining a LookML element, and a dictionary representing a LookML element.
The Dagster asset key that represents the LookML element.