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
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
We are using matrix in production and because of our usage we ended up with an essential need.
What I have:
We have some rooms with bots that post data each 15/30/60/ secs as state events (e.g. env1.metrics) with a key (e.g. api1).
The problem is that for each state_event/key, we have all the data from previous update of the event stacking in the database.
The database will eventually grow to reach the limit of allocated space. Deletion of row corresponding to the event in database make the room unusable.
What I need:
An enpoint for events/state_events deletion by id or between two date for a state_event/key, ensuring that the data and the entries are actually deleted in the database and in the room (at least when the room is not encrypted).
The text was updated successfully, but these errors were encountered:
I'm going to close this since I believe the API already exists for this. If that solution doesn't work please re-open it (or provide more information of why it doesn't).
@clokep
After testing I confirm that the API purge history delete room events like m.room.messages etc...
In the use case explained before we are using state_events like this: /_matrix/client/r0/rooms/${room}/state/project.metrics/appmetrics
When running the purge with:
Hi,
We are using matrix in production and because of our usage we ended up with an essential need.
What I have:
We have some rooms with bots that post data each 15/30/60/ secs as state events (e.g. env1.metrics) with a key (e.g. api1).
The problem is that for each state_event/key, we have all the data from previous update of the event stacking in the database.
The database will eventually grow to reach the limit of allocated space. Deletion of row corresponding to the event in database make the room unusable.
What I need:
An enpoint for events/state_events deletion by id or between two date for a state_event/key, ensuring that the data and the entries are actually deleted in the database and in the room (at least when the room is not encrypted).
The text was updated successfully, but these errors were encountered: