Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(compactor): compaction iterator support filter key with key_range #18031

Merged
merged 6 commits into from
Aug 21, 2024

Conversation

Li0k
Copy link
Contributor

@Li0k Li0k commented Aug 13, 2024

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

part 2 of #17898

After PR 17898, SstableStreamIterator will no longer read the whole object, it needs to filter block_metas and keys by key_range to ensure that the k-v pair read belongs to the current SST.

Note: This PR does not implement the logic for fast_compact.

Checklist

  • I have written necessary rustdoc comments
  • I have added necessary unit tests and integration tests
  • I have added test labels as necessary. See details.
  • I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
  • My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
  • All checks passed in ./risedev check (or alias, ./risedev c)
  • My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)
  • My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

  • My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

@Li0k Li0k requested review from hzxa21 and MrCroxx August 13, 2024 13:28
Copy link
Collaborator

@hzxa21 hzxa21 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rest LGTM

Comment on lines +291 to +304
assert!(
!self.exceed_key_range_left(key),
"key {:?} key_range_left {:?}",
key,
self.key_range_left.to_ref()
);

assert!(
!self.exceed_key_range_right(key),
"key {:?} key_range_right {:?} key_range_right_exclusive {}",
key,
self.key_range_right.to_ref(),
self.key_range_right_exclusive
);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be debug_assert?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For performance.
I think so.

For data correctness.
I think it has to be assert, when the key doesn't satisfy this condition we may give wrong output, and it can't be assumed that the user must have used FullKeyTracker externally to judge the output.
what do you think @hzxa21

@Li0k Li0k requested a review from zwang28 August 21, 2024 02:55
@Li0k Li0k added this pull request to the merge queue Aug 21, 2024
Merged via the queue into main with commit ff55fcf Aug 21, 2024
29 of 30 checks passed
@Li0k Li0k deleted the li0k/compactor_iter_key_range branch August 21, 2024 09:56
@Li0k
Copy link
Contributor Author

Li0k commented Sep 3, 2024

#15973

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants