[COMPASS-1434] Cache schema analysis results Created: 25/Jul/17 Updated: 10/Jan/24 Resolved: 08/Oct/19 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Navigation |
| Affects Version/s: | 1.8.0-beta.2, 1.9.0-dev |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Grigori Melnik (Inactive) | Assignee: | Unassigned |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
MacOS Sierra 10.12.5 |
||
| Epic Link: | COMPASS-2234 |
| Documentation Changes Summary: | This is mitigated by the introduction of tabs. |
| Description |
|
User connects to a cluster, retrieves the list of databases, chooses a specific database and a collection to do schema analysis, then switches to another collection. 1 min later she switches back to the first collection and needs to re-analyze the schema. That's annoying. This info should be cached in the session data. At least for some time before you force the user to re-analyze. |