You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
TTL (Time to Live) is an advanced feature provided by Milvus that helps clean up expired data. However, the current TTL implementation has certain limitations that affect its flexibility:
Querying Expired Data – Milvus should allow users to configure whether expired data can still be queried.
Scheduled Data Cleanup – TTL should support data cleanup at specific intervals (e.g., on a daily basis), which requires enhancing the compaction pipeline to support a deadline-based compaction strategy.
Custom Time Fields for Compaction – Users should be able to specify business-defined time fields for compaction instead of relying solely on Milvus' internal timestamps.
Is there an existing issue for this?
Is your feature request related to a problem? Please describe.
TTL (Time to Live) is an advanced feature provided by Milvus that helps clean up expired data. However, the current TTL implementation has certain limitations that affect its flexibility:
Querying Expired Data – Milvus should allow users to configure whether expired data can still be queried.
Scheduled Data Cleanup – TTL should support data cleanup at specific intervals (e.g., on a daily basis), which requires enhancing the compaction pipeline to support a deadline-based compaction strategy.
Custom Time Fields for Compaction – Users should be able to specify business-defined time fields for compaction instead of relying solely on Milvus' internal timestamps.
Customzied TTL - Only do ttl purge on certain partitionkey. user can config through a udf, like https://github.com/facebook/rocksdb/wiki/Compaction-Filter
Describe the solution you'd like.
No response
Describe an alternate solution.
No response
Anything else? (Additional Context)
No response
The text was updated successfully, but these errors were encountered: