-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[TTL] If there is no compaction, the modification to ttl may not take effect #5134
Comments
is it by design? |
In terms of design, it is right. But functionally, or logically, it is wrong. |
agreed.. if the data is not deleted by compaction, we always compare with the latest ttl duration. |
marked as known issue |
@abby-cyber please update doc |
I think this is a data error, from the view of a user. I do not agree to add to doc just as a warning. What is by design? Who designed this data error operation? |
It is a data error indeed, but it can't be addressed totally. There is a workaround: forbid alter ttl duration if already has one. |
What if this TTL tag is dropped and re-created? |
IIRC, drop TTL is achieved by alter as well. I really don't remember this behavior precisely. |
update more details in v3.4 rc
|
Please check the FAQ documentation before raising an issue
Describe the bug (required)
Your Environments (required)
uname -a
g++ --version
orclang++ --version
lscpu
a3ffc7d8
)How To Reproduce(required)
Steps to reproduce the behavior:
Expected behavior
Additional context
The text was updated successfully, but these errors were encountered: