hongbin ma created KYLIN-2031:
-
Summary: some more DimensionEncoding
Key: KYLIN-2031
URL: https://issues.apache.org/jira/browse/KYLIN-2031
Project: Kylin
Issue Type: New Feature
Shaofeng SHI created KYLIN-2032:
---
Summary: Cube build failed when partition column isn't in
dimension list
Key: KYLIN-2032
URL: https://issues.apache.org/jira/browse/KYLIN-2032
Project: Kylin
大家好：
今天在使用kylin1.5.4版本时，在同步hive元数据时报错：
Load Hive Table Metadata From Tree页面一直显示：Loading Databases.
错误信息打印在kylin.out文件
SEVERE: Servlet.service() for servlet [kylin] in context with path [/kylin]
threw exception [Handler processing failed;
nested exception is java.lang.NoClassDefFoundError:
Roger Shi created KYLIN-2028:
Summary: find-*-dependency script fail on Mac OS
Key: KYLIN-2028
URL: https://issues.apache.org/jira/browse/KYLIN-2028
Project: Kylin
Issue Type: Bug
We may not be able to reproduce the problem (at least I cannot). Both 1.5.4
and 1.5.3 works for me.
By my experience, the root cause is often HBASE_CLASSPATH was swallowed. As
a test, try below in command shell.
[root@sandbox]# export HBASE_CLASSPATH=*ABCDE*
[root@sandbox]# hbase classpath
Zhong,Jason created KYLIN-2029:
--
Summary: lookup table support count(distinct column)
Key: KYLIN-2029
URL: https://issues.apache.org/jira/browse/KYLIN-2029
Project: Kylin
Issue Type:
Zhong,Jason created KYLIN-2030:
--
Summary: lookup table support group by primary key when no derived
dimension
Key: KYLIN-2030
URL: https://issues.apache.org/jira/browse/KYLIN-2030
Project: Kylin
Hi Tongxin,
1.5.4 has no special requirement on hive version; From 1.5.3 to 1.5.4, the
kylin.sh has some change, please check whether it was the shell script
which wasn't able to detect the dependency jars correctly. Please share
with us about your finding, or if you can fix that and contribute a
query without filter on such high cardinality is not good idea for Kylin
usage.
this query will pull all data back which looks like something about ETL or
others but not OLAP relative query.
Kylin's design purpose is for aggregation query with low latency which mean
user should narrow down query
