The XmlaOlap4jCube implementation creates in its constructor a CachingMetadataReader which caches elements to avoid useless network interchanges.
But in a usecase where new members/root members can appear for example, this implementation does not suit. Could we introduce a way to turn on/off caching either at creation time or on the fly ?
I am thinking of a boolean parameter either in the XmlaOlap4jConnection which would be used each time CubeHandler.handle method is called or directly in the XmlaOlap4jCube which would be use to switch between a CachingMetadataReader and a RawMetaDataReader when calling getMetadataReader method.
By the way : is it normal that we do not use caching in CachingMetadataReader for lookupMemberRelatives method or is it an omission ?