Uh oh!
There was an error while loading. Please reload this page.
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.
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.
This completion check can fire too early in the E-2010 handoff path. In Cloud, the handoff is committed as an
EMPTY_CUMULATIVEjob; meta-service explicitly treats that as a metadata-only update to the cumulative point/count, but it also setslast_cumu_compaction_time_ms, which BE exposes aslast cumulative success time. With this|| cumulativeSuccessTimeChanged, the helper can return right after the empty cumulative handoff, before the base compaction that actually merges the delete-version rowsets has run. The affected tests inspect rowsets immediately after this helper returns, so this reintroduces the flaky early-exit window. Please keep this fast path tied to a base-compaction completion signal, or add another rowset/base-completion check before accepting cumulative success time here.