-
Notifications
You must be signed in to change notification settings - Fork 345
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
[Improvement] revisit all the purgeXXX implementations to have a consistent behavior #3685
Comments
@mchades May I take a look into this one? I think we can refer to purgeTable in RelationalCatalog as the desired behavior |
The behavior of
One issue with this behavior is that if return false, the client will not be able to obtain the specific reason for failure. Can you refer to the behavior of dropTable and then think about the behavior of purge? @zivali |
Got it. Thank you for the clarification! :)
Also, I didn't find detail implementations of |
This proposal LGTM
It's not started yet. Currently, we have already supported partition operations in the Hive catalog, but we have not yet implemented purge partition. If you are interested, you can start researching it first. |
What would you like to be improved?
we should revisit all the
purgeTable
andpurgePartition
implementations to make sure that:UnsupportedOperationException
If target purging is not supportedHow should we improve?
see above
The text was updated successfully, but these errors were encountered: