diff options
author | Richard van der Hoff <1389908+richvdh@users.noreply.github.com> | 2023-02-28 18:49:28 +0000 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-02-28 18:49:28 +0000 |
commit | 2b78981736f9004f99b1760e3e77b234f92755a7 (patch) | |
tree | cd2b98d97df09a663fec267da4130cafd0ceb377 /synapse/storage/databases/main/cache.py | |
parent | Merge branch 'master' into develop (diff) | |
download | synapse-2b78981736f9004f99b1760e3e77b234f92755a7.tar.xz |
Remove support for aggregating reactions (#15172)
It turns out that no clients rely on server-side aggregation of `m.annotation` relationships: it's just not very useful as currently implemented. It's also non-trivial to calculate. I want to remove it from MSC2677, so to keep the implementation in line, let's remove it here.
Diffstat (limited to 'synapse/storage/databases/main/cache.py')
-rw-r--r-- | synapse/storage/databases/main/cache.py | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/synapse/storage/databases/main/cache.py b/synapse/storage/databases/main/cache.py index 5b66431691..096dec7f87 100644 --- a/synapse/storage/databases/main/cache.py +++ b/synapse/storage/databases/main/cache.py @@ -266,9 +266,6 @@ class CacheInvalidationWorkerStore(SQLBaseStore): if relates_to: self._attempt_to_invalidate_cache("get_relations_for_event", (relates_to,)) self._attempt_to_invalidate_cache("get_references_for_event", (relates_to,)) - self._attempt_to_invalidate_cache( - "get_aggregation_groups_for_event", (relates_to,) - ) self._attempt_to_invalidate_cache("get_applicable_edit", (relates_to,)) self._attempt_to_invalidate_cache("get_thread_summary", (relates_to,)) self._attempt_to_invalidate_cache("get_thread_participated", (relates_to,)) |