Skip to content
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

History feature for change audit on store and record #85

Open
ghost opened this issue Jul 20, 2020 · 0 comments
Open

History feature for change audit on store and record #85

ghost opened this issue Jul 20, 2020 · 0 comments

Comments

@ghost
Copy link

ghost commented Jul 20, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants