Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(ingestion/powerbi): link cross workspace dataset into assets #11560

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

sid-acryl
Copy link
Collaborator

No description provided.

@github-actions github-actions bot added the ingestion PR or Issue related to the ingestion of metadata label Oct 8, 2024
Copy link
Collaborator

@hsheth2 hsheth2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

had a couple questions / comments, but overall seems reasonable

# set the dataset for tiles
for tile in dashboard.tiles:
if tile.dataset_id:
tile.dataset = self.dataset_registry.get(tile.dataset_id)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this dataset registry global across all workspaces?

also, do both workspaces need to be ingested for cross-workspace lineage to work? I think we might need some docs updates if so

@@ -218,6 +218,7 @@ class Report:
webUrl: Optional[str]
embedUrl: str
description: str
dataset_id: Optional[str]
dataset: Optional["PowerBIDataset"]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how do dataset_id and dataset interact? is one filled initially, and then the other populated later?

would be good to add some comments to make this more clear

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ingestion PR or Issue related to the ingestion of metadata
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants