Repository navigation
[Core] Reduce manifest logging on table drop - #14969
Merged
Merged
Conversation
huaxingao
reviewed
Jan 6, 2026
huaxingao
approved these changes
Jan 6, 2026
amogh-jahagirdar
approved these changes
Jan 6, 2026
Contributor
There was a problem hiding this comment.
LGTM, thanks @dramaticlly and @singhpk234 @huaxingao for reviewing!
This file contains hidden or 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
4 participants
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.
When dorp large table with many manifests, the CatalogUtils log every detail about manifest to be deleted and pollute the logs. Only total count of manifests to be dropped shall be sufficient, IO level logging can be selectively enabled to see exact deletion candidates
CC @huaxingao @stevenzwu