[COMPASS-4836] Investigate redundant refresh-data Created: 19/May/21 Updated: 17/May/23 Resolved: 17/May/23 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Tech debt |
| Affects Version/s: | None |
| Fix Version/s: | No version |
| Type: | Investigation | Priority: | Major - P3 |
| Reporter: | Maurizio Casimirri | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | needs-prioritization | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Documentation Changes: | Not Needed | ||||||||
| Description |
|
The 'refresh-data' event is emitted in few places, and it triggers actions in various parts of Compass. The side effects of that is not always clear and potentially causes performance issues, or unwanted behaviour. eg. in compass-collections-ddl: This ticket is for investigate those events and how they relates and potentially remove them or replace it with safer options. |