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.