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

bug: move table to an existing compaction group can violate can_concat for non-overlapping level #11703

Closed
Tracked by #6640
hzxa21 opened this issue Aug 16, 2023 · 2 comments
Assignees
Labels
type/bug Something isn't working
Milestone

Comments

@hzxa21
Copy link
Collaborator

hzxa21 commented Aug 16, 2023

Describe the bug

commit: 4a5bf065b8d3c119393856e2390763e62499e765
The following scenario can happen:

  • Compaction Group A contains tables [T1, T2, T4]
  • Compaction Group B contains tables [T3, T5]
  • T3 is moved from Group B to Group A.

When that happen, it is possible that SST1 with [T1, T2, T4] and SST1 with [T3] are in the same non-overlapping level while they actually overlap with each other.

Error message/log

No response

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

No response

Additional context

No response

@hzxa21 hzxa21 added the type/bug Something isn't working label Aug 16, 2023
@github-actions github-actions bot added this to the release-1.2 milestone Aug 16, 2023
@hzxa21
Copy link
Collaborator Author

hzxa21 commented Sep 11, 2023

@Little-Wallace IIUC, this is fixed by #11683. Shall we close the issue?

@Little-Wallace
Copy link
Contributor

fix by #11683

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants