[ISSUE #7961] use BoundaryType in binarySearchInCQByTime #7968
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.
Which Issue(s) This PR Fixes
[Enhancement] use BoundaryType in binarySearchInCQByTime #7961
Brief Description
use BoundaryType in binarySearchInCQByTime instead of absolute value comparison.
When performing a range query, pass BoundaryType.LOWER to get the left boundary msg offset, pass BoundaryType.UPPER to get the right boundary msg offset
How Did You Test This Change?
I wrote a test case, the timestamp 1711351134289 does not match an exact offset, when we call mqAdminExt.searchLowerBoundaryOffset(), it returns the offset whose storeTime is the smallest storeTime that is greater than the target storeTime. When we call mqAdminExt.searchUpperBoundaryOffset(), it returns the offset whose storeTime is the biggest storeTime that is smaller than the target storeTime.