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.
This is regarding a new feature for storing the history of changes in the stores / records.
Describe the solution you'd like
Ability to turn on a feature to record diff of changes happening on stores and records.
Optional TTL for record changes history to limit amount of data captured in the back-end.
Describe alternatives you've considered
There is no other good alternative to capture the changes for stores and records since Triton is the keeper of the data. Creating a layer on top of Triton to capture that data would not be very efficient.
Additional context
As a user of the Triton Storage service, I want an endpoint to query all the changes to a store or record. For MVP, provide a way to query by record key or store key, with the ability to list in ascending or descending modifiedAt time.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
This is regarding a new feature for storing the history of changes in the stores / records.
Describe the solution you'd like
Ability to turn on a feature to record diff of changes happening on stores and records.
Optional TTL for record changes history to limit amount of data captured in the back-end.
Describe alternatives you've considered
There is no other good alternative to capture the changes for stores and records since Triton is the keeper of the data. Creating a layer on top of Triton to capture that data would not be very efficient.
Additional context
As a user of the Triton Storage service, I want an endpoint to query all the changes to a store or record. For MVP, provide a way to query by record key or store key, with the ability to list in ascending or descending modifiedAt time.
The text was updated successfully, but these errors were encountered: