[tiering] Reduce LakeSnapshot log verbosity in TieringSplitGenerator#3700
Open
beryllw wants to merge 1 commit into
Open
[tiering] Reduce LakeSnapshot log verbosity in TieringSplitGenerator#3700beryllw wants to merge 1 commit into
beryllw wants to merge 1 commit into
Conversation
luoyuxia
approved these changes
Jul 20, 2026
beryllw
force-pushed
the
feature/reduce-tiering-log
branch
from
July 20, 2026 06:23
47755d8 to
df4f479
Compare
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
2 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.
Purpose
Linked issue: close #xxx
TieringSplitGenerator logs the full LakeSnapshot object at INFO level every time it generates splits (every tiering.poll.table.interval, default 30s). For partitioned tables with many buckets , a single log line becomes extremely long and floods out other logs needed for troubleshooting.
Brief change log
Tests
API and Format
No impact — logging-only change.
Documentation
No documentation update needed.