-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
fix(lineage): error message for edit lineage #12724
Conversation
❌ 1 Tests Failed:
View the full list of 1 ❄️ flaky tests
To view more test analytics, go to the Test Analytics Dashboard |
COPY metadata-models/src/main/resources/entity-registry.yml /datahub/datahub-gms/resources/entity-registry.yml | ||
COPY docker/datahub-gms/start.sh /datahub/datahub-gms/scripts/start.sh | ||
COPY docker/monitoring/client-prometheus-config.yaml /datahub/datahub-gms/scripts/prometheus-config.yaml | ||
RUN chmod +x /datahub/datahub-gms/scripts/start.sh | ||
COPY war.war /datahub/datahub-gms/bin/war.war |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i don't know about this flow so not sure if you want to run this by anyone else or if you feel confident
@@ -5,6 +5,8 @@ The UI shows the latest version of the data lineage. The time picker can be used | |||
|
|||
## Editing from Lineage Graph View | |||
|
|||
Ensure that you have `Edit lineage` privilege on both upstream and downstream entities before you try to add upstream or downstream lineage. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice
log.debug(String.format
tolog.debug(
on java sidewar
to later as rest of items are less frequently changed. Will very slightly help with dev workflow for gmsChecklist