[jira] [Commented] (KYLIN-1898) Upgrade to Avatica 1.8 or higher
[ https://issues.apache.org/jira/browse/KYLIN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385511#comment-15385511 ] Dayue Gao commented on KYLIN-1898: -- I've relocated kylin-jdbc dependencies in KYLIN-1846, hopefully it will solve the problem mentioned. > Upgrade to Avatica 1.8 or higher > > > Key: KYLIN-1898 > URL: https://issues.apache.org/jira/browse/KYLIN-1898 > Project: Kylin > Issue Type: Bug >Reporter: Julian Hyde > Attachments: KYLIN-1898.patch > > > A [stackoverflow > question|http://stackoverflow.com/questions/38369871/how-to-install-two-different-version-of-a-specific-package-in-maven] > reports problems when mixing Avatica 1.6 (used by Kylin) and Avatica 1.8 > (used by some unspecified other database). It appears that 1.6 and 1.8 are > not compatible, probably due to CALCITE-836 or CALCITE-1213. The solution is > for Kylin to upgrade to 1.8 or higher. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-1907) Missing items in copyUnChangedProperties during upgrading
Zhong Yanghong created KYLIN-1907: - Summary: Missing items in copyUnChangedProperties during upgrading Key: KYLIN-1907 URL: https://issues.apache.org/jira/browse/KYLIN-1907 Project: Kylin Issue Type: Bug Components: Tools, Build and Test Reporter: Zhong Yanghong Assignee: Zhong Yanghong -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1907) Missing items in copyUnChangedProperties during upgrading
[ https://issues.apache.org/jira/browse/KYLIN-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong Yanghong updated KYLIN-1907: -- Description: Missing items: statusNeedNotify, partitionDateStart, partitionDateEnd, autoMergeTimeRanges, retentionRange > Missing items in copyUnChangedProperties during upgrading > - > > Key: KYLIN-1907 > URL: https://issues.apache.org/jira/browse/KYLIN-1907 > Project: Kylin > Issue Type: Bug > Components: Tools, Build and Test >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong > > Missing items: statusNeedNotify, partitionDateStart, partitionDateEnd, > autoMergeTimeRanges, retentionRange -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1788) Allow arbitrary number of mandatory dimensions in one aggregation group
[
https://issues.apache.org/jira/browse/KYLIN-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385604#comment-15385604
]
Wang Cheng commented on KYLIN-1788:
---
Essentially it is not a bug but a strategy problem. Of course it can be solved
by tuning the threshold "maxSize", however, it's difficult to get an
appropriate size.
A compromise proposal is to count "mandatoryDims.size()" as 1 if its size isn't
zero:
{code:java}
int mandatorySize = mandatoryDims.size() > 0 ? 1 : 0 ;
if ( mandatorySize + normalDimSize + hierarchySize + jointSize > maxSize) {
context.addResult(ResultLevel.ERROR, "Aggregation group " + index + "
has too many dimensions");
continue;
}
{code}
> Allow arbitrary number of mandatory dimensions in one aggregation group
>
>
> Key: KYLIN-1788
> URL: https://issues.apache.org/jira/browse/KYLIN-1788
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v1.5.2
>Reporter: hongbin ma
>Assignee: hongbin ma
>
> To prevent one aggregation group containing too many combinations we apply a
> check
> {code:java}
> if (mandatoryDims.size() + normalDimSize + hierarchySize + jointSize >
> maxSize) {
> context.addResult(ResultLevel.ERROR, "Aggregation group " +
> index + " has too many dimensions");
> continue;
> }
> {code}
> however the formular fails to take into account the case where there're many
> mandatory dimensions. For example, if we have 50 dimensions in a cube and we
> only need the base cuboid, then what we want is a single aggregation group
> containing all the dimensions, each of them being a mandatory.
> since mandatory dimensions are more "encouraged", I suggest to remove
> counting mandatory dimensions in the formula. the revised code will be:
> {code:java}
> if (normalDimSize + hierarchySize + jointSize > maxSize) {
> context.addResult(ResultLevel.ERROR, "Aggregation group " +
> index + " has too many dimensions");
> continue;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KYLIN-1907) Missing items in copyUnChangedProperties during upgrading
[ https://issues.apache.org/jira/browse/KYLIN-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong Yanghong updated KYLIN-1907: -- Attachment: add_missing_items_in_copyUnChangedProperties_during_upgrading.patch > Missing items in copyUnChangedProperties during upgrading > - > > Key: KYLIN-1907 > URL: https://issues.apache.org/jira/browse/KYLIN-1907 > Project: Kylin > Issue Type: Bug > Components: Tools, Build and Test >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong > Attachments: > add_missing_items_in_copyUnChangedProperties_during_upgrading.patch > > > Missing items: statusNeedNotify, partitionDateStart, partitionDateEnd, > autoMergeTimeRanges, retentionRange -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1786) Frontend work for KYLIN-1313 (extended columns as measure)
[ https://issues.apache.org/jira/browse/KYLIN-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385610#comment-15385610 ] hongbin ma commented on KYLIN-1786: --- there's already 1.5.3 RC in mail list, you can try that > Frontend work for KYLIN-1313 (extended columns as measure) > -- > > Key: KYLIN-1786 > URL: https://issues.apache.org/jira/browse/KYLIN-1786 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Dong Li >Assignee: Zhong,Jason > Fix For: v1.5.3 > > Attachments: 屏幕快照 2016-06-15 12.22.54.png > > > KYLIN-1313 introduced a measure called extendedcolumn, but seems not enabled > on WebUI, see attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KYLIN-1786) Frontend work for KYLIN-1313 (extended columns as measure)
[ https://issues.apache.org/jira/browse/KYLIN-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385610#comment-15385610 ] hongbin ma edited comment on KYLIN-1786 at 7/20/16 9:40 AM: there's already 1.5.3 RC in mail list (search [VOTE] Release apache-kylin-1.5.3 (release candidate 1)), you can try that was (Author: mahongbin): there's already 1.5.3 RC in mail list, you can try that > Frontend work for KYLIN-1313 (extended columns as measure) > -- > > Key: KYLIN-1786 > URL: https://issues.apache.org/jira/browse/KYLIN-1786 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Dong Li >Assignee: Zhong,Jason > Fix For: v1.5.3 > > Attachments: 屏幕快照 2016-06-15 12.22.54.png > > > KYLIN-1313 introduced a measure called extendedcolumn, but seems not enabled > on WebUI, see attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1907) Missing items in copyUnChangedProperties during upgrading
[ https://issues.apache.org/jira/browse/KYLIN-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385618#comment-15385618 ] Zhong Yanghong commented on KYLIN-1907: --- [~mahongbin], could you help have a review of this patch? Thanks. By the way, when should the setter of property for "overrideKylinProps" in CubeDesc be private? > Missing items in copyUnChangedProperties during upgrading > - > > Key: KYLIN-1907 > URL: https://issues.apache.org/jira/browse/KYLIN-1907 > Project: Kylin > Issue Type: Bug > Components: Tools, Build and Test >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong > Attachments: > add_missing_items_in_copyUnChangedProperties_during_upgrading.patch > > > Missing items: statusNeedNotify, partitionDateStart, partitionDateEnd, > autoMergeTimeRanges, retentionRange -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1875) When do Kylin support SnowFlake schema?
[ https://issues.apache.org/jira/browse/KYLIN-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385625#comment-15385625 ] hongbin ma commented on KYLIN-1875: --- we don't > When do Kylin support SnowFlake schema? > --- > > Key: KYLIN-1875 > URL: https://issues.apache.org/jira/browse/KYLIN-1875 > Project: Kylin > Issue Type: Improvement >Affects Versions: v1.5.2 >Reporter: Rahul Choubey > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1876) Star Schema also supports more than one fact table
[ https://issues.apache.org/jira/browse/KYLIN-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385624#comment-15385624 ] hongbin ma commented on KYLIN-1876: --- Hi, how many fact tables are supposed to be there in a star schema? can you provide more reading materials? > Star Schema also supports more than one fact table > -- > > Key: KYLIN-1876 > URL: https://issues.apache.org/jira/browse/KYLIN-1876 > Project: Kylin > Issue Type: Bug >Reporter: Rahul Choubey > > As per the document of Apache Kylin, it supports Star Schema but in the Kylin > we have the option to select only one Fact Table. Is there is any planning to > support more than one Fact Table.? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1788) Allow arbitrary number of mandatory dimensions in one aggregation group
[
https://issues.apache.org/jira/browse/KYLIN-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wang Cheng updated KYLIN-1788:
--
Attachment: 0001-kylin-1788-enable-arbitrary-mandatory-size.patch
> Allow arbitrary number of mandatory dimensions in one aggregation group
>
>
> Key: KYLIN-1788
> URL: https://issues.apache.org/jira/browse/KYLIN-1788
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v1.5.2
>Reporter: hongbin ma
>Assignee: hongbin ma
> Attachments: 0001-kylin-1788-enable-arbitrary-mandatory-size.patch
>
>
> To prevent one aggregation group containing too many combinations we apply a
> check
> {code:java}
> if (mandatoryDims.size() + normalDimSize + hierarchySize + jointSize >
> maxSize) {
> context.addResult(ResultLevel.ERROR, "Aggregation group " +
> index + " has too many dimensions");
> continue;
> }
> {code}
> however the formular fails to take into account the case where there're many
> mandatory dimensions. For example, if we have 50 dimensions in a cube and we
> only need the base cuboid, then what we want is a single aggregation group
> containing all the dimensions, each of them being a mandatory.
> since mandatory dimensions are more "encouraged", I suggest to remove
> counting mandatory dimensions in the formula. the revised code will be:
> {code:java}
> if (normalDimSize + hierarchySize + jointSize > maxSize) {
> context.addResult(ResultLevel.ERROR, "Aggregation group " +
> index + " has too many dimensions");
> continue;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KYLIN-1908) Collect Metrics to JMX
kangkaisen created KYLIN-1908: - Summary: Collect Metrics to JMX Key: KYLIN-1908 URL: https://issues.apache.org/jira/browse/KYLIN-1908 Project: Kylin Issue Type: New Feature Components: Tools, Build and Test Affects Versions: v1.5.2 Reporter: kangkaisen Assignee: kangkaisen As we all known, some performance metrics is important for enterprise applications. so we should support to collect metrics to JMX in Kylin. The method I have done is As shown below: 1. use `org.apache.hadoop.metrics2` as the metrics collection framework. 2. define MBean Class for the metrics that we need to collect. 3. update metrics in right place. The questions I have: 1. can I depend on `org.apache.hadoop.metrics2` directly? 2. how do you think about my method? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1908) Collect Metrics to JMX
[ https://issues.apache.org/jira/browse/KYLIN-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387247#comment-15387247 ] Shaofeng SHI commented on KYLIN-1908: - hi kaisen, it would be nice if Kylin can expose some metrics with standard technicals; is JMX the best solution? Can you give some comments on this? Thank you. > Collect Metrics to JMX > -- > > Key: KYLIN-1908 > URL: https://issues.apache.org/jira/browse/KYLIN-1908 > Project: Kylin > Issue Type: New Feature > Components: Tools, Build and Test >Affects Versions: v1.5.2 >Reporter: kangkaisen >Assignee: kangkaisen > > As we all known, some performance metrics is important for enterprise > applications. so we should support to collect metrics to JMX in Kylin. > The method I have done is As shown below: > 1. use `org.apache.hadoop.metrics2` as the metrics collection framework. > 2. define MBean Class for the metrics that we need to collect. > 3. update metrics in right place. > The questions I have: > 1. can I depend on `org.apache.hadoop.metrics2` directly? > 2. how do you think about my method? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
