HIVE-24135: Delete DB managed directory on drop db (Naveen Gangam) #2354
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
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.
What changes were proposed in this pull request?
The database's managed location is not deleted when the database is dropped. This fix addresses the issue.
Why are the changes needed?
Even though db.getManagedLocation() might be null, there is always a default managed location for the database. On a drop database, we check to see if this location is null and only drop it if not null. But regardless of whether or not it is null, there is always an assigned location that needs to be dropped.
Does this PR introduce any user-facing change?
NO
How was this patch tested?
Unit test + manually