At first,I also think so.Howerver,after resetting the precision to 9.75%,I
find the processing time become so fast.
--
View this message in context:
http://apache-kylin.74782.x6.nabble.com/From-the-Build-Base-Cuboid-Data-step-to-Build-N-Dimension-steps-Too-much-time-is-taken-tp3351p3655.html
gt; precision is 1.2% . So the steps is too slow even though the data is
> little(million).Can I sloue the problem by reducing the value of
> kylin.job.mapreduce.default.reduce.input.mb?
>
> --
> View this message in context:
> http://apache-kylin.74782.x6.nabble.com/From-the
://apache-kylin.74782.x6.nabble.com/From-the-Build-Base-Cuboid-Data-step-to-Build-N-Dimension-steps-Too-much-time-is-taken-tp3351p3368.html
Sent from the Apache Kylin mailing list archive at Nabble.com.
ask: Task
'attempt_1452787370536_0086_m_00_0' done.
--
View this message in context:
http://apache-kylin.74782.x6.nabble.com/From-the-Build-Base-Cuboid-Data-step-to-Build-N-Dimension-steps-Too-much-time-is-taken-tp3351.html
Sent from the Apache Kylin mailing list archive at Nabble.com.