-
Notifications
You must be signed in to change notification settings - Fork 1.3k
TTL for entities in the Online stores other Than Redis #1988
Copy link
Copy link
Closed
Labels
Community Contribution NeededWe want community to contributeWe want community to contributekind/featureNew feature or requestNew feature or requestpriority/p2wontfixThis will not be worked onThis will not be worked on
Description
Metadata
Metadata
Assignees
Labels
Community Contribution NeededWe want community to contributeWe want community to contributekind/featureNew feature or requestNew feature or requestpriority/p2wontfixThis will not be worked onThis will not be worked on
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
StatusShow more project fields
Done
Is your feature request related to a problem? Please describe.
(for context: we are using the Redis online store)
At the moment, once an entity is written to the Online store, it's there until it's manually cleaned up.
In most of our business cases, the Entity will have a natural expiration time (when it's no longer relevant for the use case).
It would be nice to be able to expire the entity in the online store, with some kind of TTL setting.
Describe the solution you'd like
the issue with this is that the
ttlparam infeature_view/tableis overloaded (initially designed for a use case in the offline store)Also, in this type of setup and use case, the TTL should be on the entity level not
feature_viewbecause the Redis key bin is based on entity (feature_view ttl is designed for something else also)so the proposal:
add
online_store_ttlparam to the Entity objectexample:
Note: implementation details may vary a bit based on the Online store type