-
Notifications
You must be signed in to change notification settings - Fork 3k
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(cli) Adds side-effect report of rollbacks #4482
Merged
shirshanka
merged 7 commits into
datahub-project:master
from
pedro93:pedro/add-report-to-rollback
Mar 31, 2022
Merged
feat(cli) Adds side-effect report of rollbacks #4482
shirshanka
merged 7 commits into
datahub-project:master
from
pedro93:pedro/add-report-to-rollback
Mar 31, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@pedro93: Could you provide some sample output of these runs here? |
@shirshanka please take a look at the commit message, I've added some sample output |
shirshanka
reviewed
Mar 30, 2022
shirshanka
reviewed
Mar 30, 2022
shirshanka
reviewed
Mar 30, 2022
...let-impl/src/main/java/com/linkedin/metadata/resources/entity/BatchIngestionRunResource.java
Outdated
Show resolved
Hide resolved
shirshanka
reviewed
Mar 30, 2022
...let-impl/src/main/java/com/linkedin/metadata/resources/entity/BatchIngestionRunResource.java
Outdated
Show resolved
Hide resolved
shirshanka
reviewed
Mar 30, 2022
metadata-models/src/main/pegasus/com/linkedin/metadata/run/AspectInfo.pdl
Outdated
Show resolved
Hide resolved
shirshanka
reviewed
Mar 30, 2022
metadata-models/src/main/pegasus/com/linkedin/metadata/run/AspectInfo.pdl
Outdated
Show resolved
Hide resolved
shirshanka
approved these changes
Mar 30, 2022
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.
LGTM! Will merge after CI is green 👍
maggiehays
pushed a commit
to maggiehays/datahub
that referenced
this pull request
Aug 1, 2022
…t#4482) Co-authored-by: Shirshanka Das <shirshanka@apache.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR improves on #4405 on several fronts:
aspectsReverted
inRollbackResponse
's pdl definition.--soft/--nuke
respectively to be in line with other flags in the command line tool.datahub get
command default behaviour to return all aspects of a given entity if no aspect was specified.Sample output of rolling back an ingestion that produced a dataset which had it's description changed by another run:
Soft rollback (default) will rollback everything in the ingestion run except for dataset key
A hard rollback (will include key aspects):
The
WARNING
message at the end will report how many entities have aspects that will be affected by this rollback and the total number of affected aspects, if any exists.In case such aspects exist, a folder (by default
rollback-reports
, can be overridden by the--report-dir
flag) will be created with the following file structurerollback-reports/{time}/<files>
as seen below:config.json
is for now a simple json containing information of which run_id was processed.unsafe_entities.csv
is a csv with a single column (urn), for now, for datahub operators to know which entities have unsafe aspects. NOTE we have set a maximum of 1 million entities to be sent from the backend to not overload the network when sending these results back.To know which aspects are affected, the datahub operator must run
datahub get --urn <urn in unsafe_entities.csv>
. The output will be set the aspects where not part of the rollback and are now considered unsafe.The
rollback.csv
will save the table presented by the command into a file to datahub users to keep a reference of what was touched by the rollback.Checklist