Thanks for your replies. Here is the jira about this feature. The PR are being
prepared. Hoping for more advices from yours.
https://issues.apache.org/jira/browse/KYLIN-3982
Regards
yuzhang
| |
yuzhang
|
|
shifengdefan...@163.com
|
签名由网易邮箱大师定制
On 4/26/2019 17:05，Iñigo Martínez wrote：
+1
Hi Yuzhang,
Please open a JIRA for this enhancement; If it can be implemented in an
elegant way, that will be great!
Best regards,
Shaofeng Shi 史少锋
Apache Kylin PMC
Email: shaofeng...@apache.org
Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
Join Kylin user mail group:
Hi Shaofeng:
We also take some experiment for add measure after cube be built and
encountered byte error at the very start. The default mapping strategy between
HBase store and measure definition is "multiple measures are stored in one
column of column family", which may cause byte error
Hi Yuzhang,
Glad to see such a discussion; How to support "schema change" in a friendly
way is what we should do in the next phase, as we see this requirement is
stronger than before.
Last week I also did a try on 1) adding a dimension after cube be built,
and 2) adding a measure after cube be
Hi JiaTao:
Maybe it's necessary that there is an optional auto-complete machanism
among different measure's view, isn't it?
yuzhang
| |
yuzhang
|
|
shifengdefan...@163.com
|
签名由网易邮箱大师定制
On 4/20/2019 11:38，JiaTao Tao wrote：
Hi
The idea that supports Kylin adding measures dynamically is
Hi
The idea that supports Kylin adding measures dynamically is impressive.
But in my opinion, once you add a measure, the existing segments should
also calculate the new measure(just add a new measure column). Users can
have many cubes, a cube can have many segments, if measure's view is
Hi dear kylin users and develop team:
Here have some things I want to discuss with community.
As a representative of MOLAP engine, kylin uses pre-aggregation strategies to
provide high-concurrency and second-level response analysis capabilities, but
also loses some flexibility.
The limitation
