Hi, guys,

We are wondering how kylin keep cube and cubedesc to be versionized. For 
example, if we modify the current cubedesc, e.g. 

adding or deleteing one dimension, and when we save the cube info the older 
cube would be overlapped and queries over the 

older version cube would be impossible. 

Question is : Does kylin had some strategies of versionizing the cube info ? If 
so, how would that be implemented ? 

Any available hints shall be appreciated. 

Best,
Sun.



[email protected]

Reply via email to