Almost true; You can think Kylin is 64 bit, in theory it supports up to 63 dimension in one cube;
There is no plan to extend to 128 or more in near term I believe; Since in most of the cases the dimension number wouldn't exceed 20, 64 is already "redundant" and causing extra space; With so many dimensions, there must be room for optimization; You can try some ways like: 1) extract some columns to lookup tables, and create them as "derived" dimension in the cube; 2) or create multiple cubes, each serving a part of these columns; If you have other way, please also share with the community; Thanks; 2016-06-18 0:01 GMT+08:00 Victoria Tskhay <[email protected]>: > Hello, > > It looks like the max number of dimensions in one cube is 62, is that > correct? > > We would like to add more than that. That may sound crazy, I know, but we > have a special case where all the dimensions have low cardinality (3) and > the data is very sparse. We already tried with 62 dimensions and it works > great. > > Is there any way to work around that limit? What would you suggest? Thank > you! > > > > Best regards > -- > Victoria Tskhay > > *Java Backend Developer*I glispa GmbH > > Sonnenburger Straße 73, 10437 Berlin, Germany > E [email protected] <// > e.mail.ru/compose/?mailto=mailto%[email protected]> > Skype: vikatskhay I www.glispa.com <http://www.glispa.com> > > Sitz Berlin, AG Charlottenburg HRB 114678B > -- Best regards, Shaofeng Shi
