-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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): support recursive deletes #8709
feat(cli): support recursive deletes #8709
Conversation
Currently only works on single urns and requires browsepathv2 to be ingested for it to work correctly.
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.
Couple nits but LGTM
andFilters += [ | ||
{ | ||
"field": "platformInstance", | ||
"values": [platform_instance], | ||
"condition": "EQUAL", | ||
} | ||
] |
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.
Just curious, how is this field set in elasticsearch? Based on urn or based on dataplatforminstance aspect?
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.
the latter
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.
We should properly produce this aspect then, like in a work unit processor
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.
strongly agree - we're not consistent with it right now
Currently only works on single urns and requires browsepathv2 to be ingested for it to work correctly.
Closes #8709.
Checklist