[COMPASS-4744] `refresh-data` triggered when unnecessary Created: 01/Apr/21  Updated: 17/May/23

Status: Ready for Work
Project: Compass
Component/s: State Management, Tech debt
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Maurizio Casimirri Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by COMPASS-4836 Investigate redundant refresh-data Closed
Story Points: 5
Sprint: Iteration Orlando, Iteration Phnom Penh

 Description   

Crud, aggregate and index compass tabs reacts to the `refresh-data` event that is triggered by operations that should not cause data to be reloaded.

For example:

  • when a database or a collection is created or dropped there is no reason to reload documents in any of the tabs: if those are new the docs wont be affected until switching, if is the current db or collection it would make no sense to reload data from a non existing db or collection.
  • when an index is added or dropped there is no need to reload anything except in the index tab. Although the queries execution could potentially be affected the data would not.
  • when the query bar query changes there is no reason to reload the aggregation document in input as the input docs for a pipeline does not depend on the query

We should consider avoiding to trigger `refresh-data` in those cases and either replace it with a more specific event that would not cause unexpected behaviour (ie. `database-created`) or simply avoid triggering any event unless needed.


Generated at Wed Feb 07 22:37:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.