Syntax error in Kylin - even though query works in Hive

Here's a query that works in Hive, but gives a syntax error in Kylin. Any idea why? select part_dt, kylin_sales.LEAF_CATEG_ID, LSTG_FORMAT_NAME, LSTG_SITE_ID, META_CATEG_NAME, sum(price), max(price), min(price) from kylin_sales INNER JOIN DEFAULT.KYLIN_CATEGORY_GROUPINGS as

Re: SEVERE logs when installing Kylin-Hbase1.x on a HDP cluster

Greetings, Could someone give me some tips on resolving this issue please. 1) Do I have to fix the warning about capacity-scheduler JARS ? (According to our Hadoop Admins, they cannot find this folder in any of the nodes.We are running HortonWorks 2.4.2) "WARNING: Failed to process JAR

RE: Empty Cube

The range is up to 2015 and that’s not the problem. The only query that doesn’t return zero/empty result is from table kylin_cal_dt. When I delete this table from hive, still the result is not empty and Kylin doesn’t complain! Where does Kylin bring the data of this table even when it’s not on

Re: Query worked in Hive but not in Kylin

Roberto is correct: although "LEAF_CATEG_ID" was not explicitly defined as a dimension, it was added as a dimension since other "derived" dimensions need be derived from it on the fly (since it is a part of the PK). thank you Roberto! 2016-09-06 22:22 GMT+08:00 Roberto Tardío Olmos

Re: Query worked in Hive but not in Kylin

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

Re: Documentation on how data is stored

I dont have more info about this But,Kylin - 1453 v1.5.2 Shardin: must be a great feature (and affect to to Key Compose) - before: used hash of key - now: uses hash of column In true, I have too many doubts :) 2016-09-06 9:44 GMT+02:00

Query worked in Hive but not in Kylin

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

Re: Documentation on how data is stored

I have this picture: (I found this info in a PPT) [image: Imágenes integradas 1] Remember that you can encode dim, by dictionarty or fix length 2016-09-06 1:57 GMT+02:00 Something Something : > Hello, > > Is there any documentation available on how Kylin stores data