Almost true; You can think Kylin is 64 bit, in theory it supports up to 63
dimension in one cube;
There is no plan to extend to 128 or more in near term I believe; Since in
most of the cases the dimension number wouldn't exceed 20, 64 is already
"redundant" and causing extra space;
With so many
大家好:
在cube构建时,根据cube 设计时,measure可以有不同的聚合函数。我想找到根据不同的聚合函数来做计算的源码,但是在
// Phase 3: Build Cube
addLayerCubingSteps(result, jobId, cuboidRootPath); // layer cubing, only
selected algorithm will execute
result.addTask(createInMemCubingStep(jobId, cuboidRootPath)); // inmem cubing,
only selected
Hello,
It looks like the max number of dimensions in one cube is 62, is that
correct?
We would like to add more than that. That may sound crazy, I know, but
we have a special case where all the dimensions have low cardinality (3)
and the data is very sparse. We already tried with 62
Hi ,
I am trying to connect Kylin with Mondrian.
Jars i am using are :
kylin-jdbc-1.0-incubating.jar
olap4j.1.2
mondrian-4.4-lagunitas-SNAPSHOT-with-kylin-dialect
I am getting below error:
Exception in thread "main" java.lang.NoClassDefFoundError:
mondrian/xmla/XmlaHandler$XmlaExtra
by default the web UI only shows the jobs in LAST ONE WEEK, pls have a
check.
2016-06-17 16:58 GMT+08:00 Jie Tao :
> actually I discarded all jobs and I do not see any ERROR job in the
> Monitor view of Kylin UI.
>
> Where can I see these error jobs?
>
> Jie
>
>
> Am
actually I discarded all jobs and I do not see any ERROR job in the
Monitor view of Kylin UI.
Where can I see these error jobs?
Jie
Am 17.06.2016 um 10:31 schrieb ShaoFeng Shi:
Hi Jie,
If a job is "ERROR", the intermediate hive table of it will not be dropped,
as "ERROR" is not a final
Hi Jie,
If a job is "ERROR", the intermediate hive table of it will not be dropped,
as "ERROR" is not a final state; User can resume an "Error" job at any
time, so Kylin skipped to cleanup for that.
If you discard these error jobs, and re-run the cleanup, the intermediate
hive table will be
Zhong Yanghong created KYLIN-1805:
-
Summary: It's easily got stuck when deleting HTables during
running the StorageCleanupJob
Key: KYLIN-1805
URL: https://issues.apache.org/jira/browse/KYLIN-1805
You are correct, the intermediate tables are left by fail-building. I do
clean up storage based on the linked guide. Intermediate data in HDFS
and Hbase are deleted, but the intermediate tables in Hive not. The
command shows the tables but do not drop them. I donot have a lookup
table but my
BTW, are you using a view as lookup table?
2016-06-17 15:15 GMT+08:00 ShaoFeng Shi :
> This is common; If you have a job failed in between, and you discard that
> job, the "Garbage collection" step will not be executed, so the garbages
> will be left there.
>
> This is
This is common; If you have a job failed in between, and you discard that
job, the "Garbage collection" step will not be executed, so the garbages
will be left there.
This is why we still recommend user to run offline cleanup every some
period; It is not perfert, but be good for most scenarios:
Woo... something new to me. Anybody knows?
On Tue, Jun 14, 2016 at 6:57 PM, Jie Tao wrote:
> Kylin actually drops useless intermediate tables after cube building, but
> I still see one "kylin_intermediate_cubename_searchdata" table for each
> cube building in Hive. Are
Roger Shi created KYLIN-1804:
Summary: Better view for hierarchy dimensions adding when creating
cube
Key: KYLIN-1804
URL: https://issues.apache.org/jira/browse/KYLIN-1804
Project: Kylin
Issue
Yerui Sun created KYLIN-1803:
Summary: ExtendedColumn Measure Encoding with Non-ascii Characters
Key: KYLIN-1803
URL: https://issues.apache.org/jira/browse/KYLIN-1803
Project: Kylin
Issue Type:
14 matches
Mail list logo