-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[ENH] Handle one-off compaction message in compaction manager #3379
[ENH] Handle one-off compaction message in compaction manager #3379
Conversation
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
b4533be
to
6adc66c
Compare
30b27ce
to
45b2fe6
Compare
6adc66c
to
f04bbfa
Compare
45b2fe6
to
25ff5ed
Compare
f04bbfa
to
ccf3eb3
Compare
fe94965
to
2e0c103
Compare
|
||
tracing::info!("Running {} compaction jobs", job_futures.len()); | ||
|
||
job_futures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice cleanup
&mut self, | ||
compacted: &mut Vec<CollectionUuid>, | ||
) -> (u32, u32) { | ||
pub(crate) async fn compact_batch(&mut self) -> Vec<CollectionUuid> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did we change the interface of this away from num success/failed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The old interface seemed strange for me. We are able to tell the number of successful compactions using the length of the returned Vec
. The number of successful/failed compactions are only examined in one test case, and not used anywhere else. I updated the interface so that it looks cleaner to me.
2245609
to
b9521bc
Compare
2e0c103
to
d2d6721
Compare
d2d6721
to
e3fac40
Compare
Description of changes
Summarize the changes made by this PR.
Test plan
How are these changes tested?
pytest
for python,yarn test
for js,cargo test
for rustDocumentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?