Hi,
I think this is due in kylin_sales_cube you define a dimension derived
from DEFAULT.KYLIN_CATEGORY_GROUPINGS. Because of this, the derived
dimensions columns (USER_DEFINED_FIELD1, USER_DEFINED_FIELD3, UPD_DATE,
UDP_USER) are not included on HBase MOLAP cube. They are derived "on
the fly" (I have my doubts about the inner workings) from FKs,
LEAF_CATEG_ID and SITE_ID, that you have defined in Kylin data model.
These columns, LEAF_CATEG_ID and SITE_ID, are really included in MOLAP.
Thus, you can use them as dimensions in your queries.
Regards,
||
El 06/09/2016 a las 9:50, Something Something escribió:
When I ran this:
select part_dt, LEAF_CATEG_ID, SELLER_ID, sum(price), max(price),
min(price) from kylin_sales group by part_dt, LEAF_CATEG_ID, SELLER_ID
order by part_dt, LEAF_CATEG_ID, SELLER_ID;
It worked in Hive but not in Kylin. After debugging I realized it was
because 'SELLER_ID' is not a Dimension so I tried this & it worked:
select part_dt, LEAF_CATEG_ID, LSTG_FORMAT_NAME, sum(price),
max(price), min(price) from kylin_sales group by part_dt,
LEAF_CATEG_ID, LSTG_FORMAT_NAME order by part_dt, LEAF_CATEG_ID,
LSTG_FORMAT_NAME;
'cause LSTG_FORMAT_NAME is a Dimension.
Which begs a question, even though LEAF_CATEG_ID is NOT dimension,
how come Kylin didn't complain? Cleary, I am not understanding
something basic. Sorry for the dumb question, but please help. Thanks.
--
*Roberto Tardío Olmos*
/Big Data & Business Intelligence Consultant/
Avenida de Brasil, 17, Planta 16.
28020 Madrid
Fijo: 91.788.34.10
