[#8199] improvement(core): correct lock type in TreeLock log messages #8268
Conversation
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
…k type instead of overall lockType
yuqi1129
approved these changes
Aug 26, 2025
diqiu50
pushed a commit
to diqiu50/gravitino
that referenced
this pull request
Sep 15, 2025
…ssages (apache#8268) ### What changes were proposed in this pull request? Fixed log messages in `TreeLock.lock()` and `TreeLock.unlock()` to output the actual lock type (`type`) used. ### Why are the changes needed? Reflect the real lock type applied at each node at log. Fix: apache#8199 ### Does this PR introduce _any_ user-facing change? Yes, Log messages will now output the actual lock type in `TreeLock.lock()` and `TreeLock.unlock()`. ### How was this patch tested? Verified log output manually during lock/unlock operations.
bharos
pushed a commit
to bharos/gravitino
that referenced
this pull request
Oct 3, 2025
…ssages (apache#8268) ### What changes were proposed in this pull request? Fixed log messages in `TreeLock.lock()` and `TreeLock.unlock()` to output the actual lock type (`type`) used. ### Why are the changes needed? Reflect the real lock type applied at each node at log. Fix: apache#8199 ### Does this PR introduce _any_ user-facing change? Yes, Log messages will now output the actual lock type in `TreeLock.lock()` and `TreeLock.unlock()`. ### How was this patch tested? Verified log output manually during lock/unlock operations.
bharos
pushed a commit
to bharos/gravitino
that referenced
this pull request
Oct 7, 2025
…ssages (apache#8268) ### What changes were proposed in this pull request? Fixed log messages in `TreeLock.lock()` and `TreeLock.unlock()` to output the actual lock type (`type`) used. ### Why are the changes needed? Reflect the real lock type applied at each node at log. Fix: apache#8199 ### Does this PR introduce _any_ user-facing change? Yes, Log messages will now output the actual lock type in `TreeLock.lock()` and `TreeLock.unlock()`. ### How was this patch tested? Verified log output manually during lock/unlock operations.
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.
What changes were proposed in this pull request?
Fixed log messages in
TreeLock.lock()andTreeLock.unlock()to output the actual lock type (type) used.Why are the changes needed?
Reflect the real lock type applied at each node at log.
Fix: #8199
Does this PR introduce any user-facing change?
Yes, Log messages will now output the actual lock type in
TreeLock.lock()andTreeLock.unlock().How was this patch tested?
Verified log output manually during lock/unlock operations.