to control the query
> time delay and the size of cube, while your data set is big. So the
> Optimization is seriously necessary ! Try to get something from
> https://www.gitbook.com/@kyligence
>
> Good Luck!
>
> --
> View this message in context: http://apache-kylin.7478
is big. So the
Optimization is seriously necessary ! Try to get something from
https://www.gitbook.com/@kyligence
Good Luck!
--
View this message in context:
http://apache-kylin.74782.x6.nabble.com/No-build-all-dimensions-tp7263p7264.html
Sent from the Apache Kylin mailing list archive
.
Then when queried, we calcutale the result set according to the results of
11 cuboids.
Does anyone have some ideas?
Maybe we can discuss about it.
--
View this message in context:
http://apache-kylin.74782.x6.nabble.com/No-build-all-dimensions-tp7263.html
Sent from the Apache Kylin mailing
