-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Broken moving to S3 by TTL data parts that created in 24.1 to S3 after upgrade to 24.2 #63700
Comments
It proofs nothing. |
After inserting the data I immediately updated to 24.2. After update TTL for parts that created in 24.1 doesn't work. |
OK, what if you just restart 24.1 ? I guess it will be the same. And it's expected behaviour, and I can explain it. |
Ive done as you say: inserted data in CH 24.1 and immediately restart. TTL finished correctly. This behavior is diffrent if instead of restarting I do an update to 24.2. |
I use Clickhouse 24.1
I've created table and filled with data with TTL (move to S3).
Update Clickhouse to 24.2.
Old parts are not moved to S3 after the TTL expires. There are no problem with new parts.
Example:
Expected behavior
Expected that parts will move to S3.
The text was updated successfully, but these errors were encountered: