[jira] [Updated] (KYLIN-2881) Improve hbase coprocessor exception handling at kylin server side
[
https://issues.apache.org/jira/browse/KYLIN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhong Yanghong updated KYLIN-2881:
--
Attachment: APACHE-KYLIN-2881.patch
> Improve hbase coprocessor exception handling at kylin server side
> --
>
> Key: KYLIN-2881
> URL: https://issues.apache.org/jira/browse/KYLIN-2881
> Project: Kylin
> Issue Type: Improvement
> Components: Query Engine
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
> Fix For: v2.3.0
>
> Attachments: APACHE-KYLIN-2881.patch
>
>
> A query may need a bunch of hconnections to visit hbase. Anyone of them
> fails, the whole query should be interrupted, and all of the related
> hconnections should be released for future other queries despite that
> currently we cannot interrupt the threads at hbase coprocessor side.
> To achieve this goal, one property is added to QueryContext to keep
> {{Throwable}}. If any sub-step during the query detects this {{Throwable}},
> it should stop. In {{ExpectedSizeIterator}}, there are two parts where this
> detection is needed.
> * before putting data to the queue
> * during iteration
> If exception happens during a query, it should stop its related threads.
> Thus, {{QueryStopListener}} is added for this.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KYLIN-3098) add a new config kylin.query.max-return-rows for the maximum row count returned to user
[
https://issues.apache.org/jira/browse/KYLIN-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285609#comment-16285609
]
Zhong Yanghong commented on KYLIN-3098:
---
In some cases that lots of post-aggregations are needed, the scan limitation
will fail fast. However, it may bring additional issues. For examples, when
query hits base cuboid with large row count(bytes), it will always throw
{{ResourceLimitExceededException}}.
> add a new config kylin.query.max-return-rows for the maximum row count
> returned to user
> ---
>
> Key: KYLIN-3098
> URL: https://issues.apache.org/jira/browse/KYLIN-3098
> Project: Kylin
> Issue Type: Improvement
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
> Attachments: APACHE-KYLIN-3098.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KYLIN-3099) Add restart operation for kylin.sh
[ https://issues.apache.org/jira/browse/KYLIN-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated KYLIN-3099: Attachment: 0001-KYLIN-3099-Add-restart-operation-for-kylin.sh.patch Issue Type: New Feature (was: Improvement) > Add restart operation for kylin.sh > -- > > Key: KYLIN-3099 > URL: https://issues.apache.org/jira/browse/KYLIN-3099 > Project: Kylin > Issue Type: New Feature > Components: General >Affects Versions: v2.3.0 >Reporter: peng.jianhua >Assignee: peng.jianhua > Labels: patch > Attachments: 0001-KYLIN-3099-Add-restart-operation-for-kylin.sh.patch > > > When I want to restart kylin server, I should execute stop operation, then > execute start operation, I think this is very troublesome, it is more > convenient to add a restart operation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-3098) add a new config kylin.query.max-return-rows for the maximum row count returned to user
[ https://issues.apache.org/jira/browse/KYLIN-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong Yanghong updated KYLIN-3098: -- Attachment: APACHE-KYLIN-3098.patch > add a new config kylin.query.max-return-rows for the maximum row count > returned to user > --- > > Key: KYLIN-3098 > URL: https://issues.apache.org/jira/browse/KYLIN-3098 > Project: Kylin > Issue Type: Improvement >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong > Attachments: APACHE-KYLIN-3098.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-3099) Add restart operation for kylin.sh
peng.jianhua created KYLIN-3099: --- Summary: Add restart operation for kylin.sh Key: KYLIN-3099 URL: https://issues.apache.org/jira/browse/KYLIN-3099 Project: Kylin Issue Type: Improvement Components: General Affects Versions: v2.3.0 Reporter: peng.jianhua Assignee: peng.jianhua When I want to restart kylin server, I should execute stop operation, then execute start operation, I think this is very troublesome, it is more convenient to add a restart operation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-3098) add a new config kylin.query.max-return-rows for the maximum row count returned to user
Zhong Yanghong created KYLIN-3098: - Summary: add a new config kylin.query.max-return-rows for the maximum row count returned to user Key: KYLIN-3098 URL: https://issues.apache.org/jira/browse/KYLIN-3098 Project: Kylin Issue Type: Improvement Reporter: Zhong Yanghong Assignee: Zhong Yanghong -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-3097) A few spell error in partials directory
[ https://issues.apache.org/jira/browse/KYLIN-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated KYLIN-3097: Description: At the beginning ,I found that the comments of 'badQuery.html' was the same as 'jobList.html'. And I check other html comments in 'partical' dictionary by the way. > A few spell error in partials directory > --- > > Key: KYLIN-3097 > URL: https://issues.apache.org/jira/browse/KYLIN-3097 > Project: Kylin > Issue Type: Bug >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Trivial > Attachments: > 0001-KYLIN-3097-A-few-spell-error-in-partials-directory.patch > > > At the beginning ,I found that the comments of 'badQuery.html' was the same > as 'jobList.html'. > And I check other html comments in 'partical' dictionary by the way. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-3097) A few spell error in partials directory
[ https://issues.apache.org/jira/browse/KYLIN-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated KYLIN-3097: Attachment: 0001-KYLIN-3097-A-few-spell-error-in-partials-directory.patch > A few spell error in partials directory > --- > > Key: KYLIN-3097 > URL: https://issues.apache.org/jira/browse/KYLIN-3097 > Project: Kylin > Issue Type: Bug >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Trivial > Attachments: > 0001-KYLIN-3097-A-few-spell-error-in-partials-directory.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-3097) A few spell error in partials directory
peng.jianhua created KYLIN-3097: --- Summary: A few spell error in partials directory Key: KYLIN-3097 URL: https://issues.apache.org/jira/browse/KYLIN-3097 Project: Kylin Issue Type: Bug Reporter: peng.jianhua Assignee: peng.jianhua Priority: Trivial -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-3089) Query exception on SortedIteratorMergerWithLimit
[
https://issues.apache.org/jira/browse/KYLIN-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285546#comment-16285546
]
Yang Hao commented on KYLIN-3089:
-
s1: cn:？？？
s2: s2: cn:苏
The comparasion is different between string and changing it to
ImmutableBytesWritable which is used for HFile
{code:java}
public ImmutableBytesWritable getImmutable(String s) {
ImmutableBytesWritable key = new ImmutableBytesWritable();
Text text = new Text(s);
key.set(text.getBytes(), 0, text.getLength());
return key;
}
public void order(String s1, String s2) {
System.out.println("compare use string: " + s1.compareTo(s2));
System.out.println("compare use ImmutableBytesWritable: " +
getImmutable(s1).compareTo(getImmutable(s2)));
}
@Test
public void test_order() {
order("cn:？？？", "cn:\uD83D\uDE0A苏\uD83D\uDE0A");
}
{code}
> Query exception on SortedIteratorMergerWithLimit
>
>
> Key: KYLIN-3089
> URL: https://issues.apache.org/jira/browse/KYLIN-3089
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v2.1.0
>Reporter: Yang Hao
>
> The executing error only exists on some special case. I have a simple sql,
> and the query is routing onto SortedIteratorMergerWithLimit. When iterate
> data, it triggers such error
> {code:java}
>//TODO: remove this check when validated
> if (last != null) {
> if (comparator.compare(last, fetched) > 0)
> throw new IllegalStateException("Not sorted! last: " +
> last + " fetched: " + fetched);
> }
> {code}
> sql is as belows.
> {code:java}
> select "DATE",appid,dim_1,dim_2, sum(uv) as uv
> from table_1
> where appid = and "DATE" = 2017
> group by "DATE",appid,dim_1,dim_2
> limit 5
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KYLIN-2736) Use multiple threads to calculate HyperLogLogPlusCounter in FactDistinctColumnsMapper
[ https://issues.apache.org/jira/browse/KYLIN-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong Yanghong updated KYLIN-2736: -- Attachment: (was: APACHE-KYLIN-2736.patch) > Use multiple threads to calculate HyperLogLogPlusCounter in > FactDistinctColumnsMapper > - > > Key: KYLIN-2736 > URL: https://issues.apache.org/jira/browse/KYLIN-2736 > Project: Kylin > Issue Type: Improvement >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong > Fix For: v2.3.0 > > Attachments: APACHE-KYLIN-2736.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2736) Use multiple threads to calculate HyperLogLogPlusCounter in FactDistinctColumnsMapper
[ https://issues.apache.org/jira/browse/KYLIN-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong Yanghong updated KYLIN-2736: -- Attachment: APACHE-KYLIN-2736.patch > Use multiple threads to calculate HyperLogLogPlusCounter in > FactDistinctColumnsMapper > - > > Key: KYLIN-2736 > URL: https://issues.apache.org/jira/browse/KYLIN-2736 > Project: Kylin > Issue Type: Improvement >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong > Fix For: v2.3.0 > > Attachments: APACHE-KYLIN-2736.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (KYLIN-2736) Use multiple threads to calculate HyperLogLogPlusCounter in FactDistinctColumnsMapper
[
https://issues.apache.org/jira/browse/KYLIN-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285535#comment-16285535
]
Zhong Yanghong edited comment on KYLIN-2736 at 12/11/17 5:50 AM:
-
Yes, this will cause CPU over-subscription. However, I think there should be a
way to enable this feature to speed up the process.
The thread number mainly depends on the how many cuboids are there whose
statistics needs to be calculated. The detailed code is as follows:
{code}
private int getStatsThreadNum(int cuboidNum) {
int unitNum =
cubeDesc.getConfig().getCuboidNumberPerStatisticsCalculator();
if (unitNum <= 0) {
logger.warn("config from getCuboidNumberPerStatisticsCalculator() "
+ unitNum + " is should larger than 0");
logger.info("Will use single thread for cuboid statistics
calculation");
return 1;
}
int calculatorNum = (cuboidNum - 1) / unitNum + 1;
if (calculatorNum >
cubeDesc.getConfig().getCuboidStatisticsCalculatorMaxNumber()) {
calculatorNum =
cubeDesc.getConfig().getCuboidStatisticsCalculatorMaxNumber();
}
return calculatorNum;
}
{code}
was (Author: yaho):
Yes, this will cause CPU over-subscription. However, I think there should be a
way to enable this feature to speed up the process.
The thread number mainly depends on the how many cuboids are there whose
statistics needs to be calculated. The detailed code is as follows:
{code}
private int getStatsThreadNum(int cuboidNum) {
int unitNum =
cubeDesc.getConfig().getCuboidNumberPerStatisticsCalculator();
if (unitNum <= 0) {
logger.warn("config from getCuboidNumberPerStatisticsCalculator() "
+ unitNum + " is should larger than 0");
logger.info("Will use single thread for cuboid statistics
calculation");
return 1;
}
int calculatorNum = (cuboidNum - 1) / unitNum + 1;
if (cuboidNum >
cubeDesc.getConfig().getCuboidStatisticsCalculatorMaxNumber()) {
calculatorNum =
cubeDesc.getConfig().getCuboidStatisticsCalculatorMaxNumber();
}
return calculatorNum;
}
{code}
> Use multiple threads to calculate HyperLogLogPlusCounter in
> FactDistinctColumnsMapper
> -
>
> Key: KYLIN-2736
> URL: https://issues.apache.org/jira/browse/KYLIN-2736
> Project: Kylin
> Issue Type: Improvement
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
> Fix For: v2.3.0
>
> Attachments: APACHE-KYLIN-2736.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (KYLIN-2736) Use multiple threads to calculate HyperLogLogPlusCounter in FactDistinctColumnsMapper
[
https://issues.apache.org/jira/browse/KYLIN-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285535#comment-16285535
]
Zhong Yanghong edited comment on KYLIN-2736 at 12/11/17 5:48 AM:
-
Yes, this will cause CPU over-subscription. However, I think there should be a
way to enable this feature to speed up the process.
The thread number mainly depends on the how many cuboids are there whose
statistics needs to be calculated. The detailed code is as follows:
{code}
private int getStatsThreadNum(int cuboidNum) {
int unitNum =
cubeDesc.getConfig().getCuboidNumberPerStatisticsCalculator();
if (unitNum <= 0) {
logger.warn("config from getCuboidNumberPerStatisticsCalculator() "
+ unitNum + " is should larger than 0");
logger.info("Will use single thread for cuboid statistics
calculation");
return 1;
}
int calculatorNum = (cuboidNum - 1) / unitNum + 1;
if (cuboidNum >
cubeDesc.getConfig().getCuboidStatisticsCalculatorMaxNumber()) {
calculatorNum =
cubeDesc.getConfig().getCuboidStatisticsCalculatorMaxNumber();
}
return calculatorNum;
}
{code}
was (Author: yaho):
Yes, this will cause CPU over-subscription. However, I think there should be a
way to enable this feature to speed up the process.
The thread number mainly depends on the how many cuboids are there whose
statistics needs to be calculated. The detailed code is as follows:
{code}
{
int unitNum =
cubeDesc.getConfig().getCuboidNumberPerStatisticsCalculator();
if (unitNum <= 0) {
logger.warn("config from getCuboidNumberPerStatisticsCalculator() "
+ unitNum + " is should larger than 0");
logger.info("Will use single thread for cuboid statistics
calculation");
return 1;
}
int calculatorNum = (cuboidNum - 1) / unitNum + 1;
if (cuboidNum >
cubeDesc.getConfig().getCuboidStatisticsCalculatorMaxNumber()) {
calculatorNum =
cubeDesc.getConfig().getCuboidStatisticsCalculatorMaxNumber();
}
return calculatorNum;
}
{code}
> Use multiple threads to calculate HyperLogLogPlusCounter in
> FactDistinctColumnsMapper
> -
>
> Key: KYLIN-2736
> URL: https://issues.apache.org/jira/browse/KYLIN-2736
> Project: Kylin
> Issue Type: Improvement
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
> Fix For: v2.3.0
>
> Attachments: APACHE-KYLIN-2736.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KYLIN-2736) Use multiple threads to calculate HyperLogLogPlusCounter in FactDistinctColumnsMapper
[
https://issues.apache.org/jira/browse/KYLIN-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285535#comment-16285535
]
Zhong Yanghong commented on KYLIN-2736:
---
Yes, this will cause CPU over-subscription. However, I think there should be a
way to enable this feature to speed up the process.
The thread number mainly depends on the how many cuboids are there whose
statistics needs to be calculated. The detailed code is as follows:
{code}
{
int unitNum =
cubeDesc.getConfig().getCuboidNumberPerStatisticsCalculator();
if (unitNum <= 0) {
logger.warn("config from getCuboidNumberPerStatisticsCalculator() "
+ unitNum + " is should larger than 0");
logger.info("Will use single thread for cuboid statistics
calculation");
return 1;
}
int calculatorNum = (cuboidNum - 1) / unitNum + 1;
if (cuboidNum >
cubeDesc.getConfig().getCuboidStatisticsCalculatorMaxNumber()) {
calculatorNum =
cubeDesc.getConfig().getCuboidStatisticsCalculatorMaxNumber();
}
return calculatorNum;
}
{code}
> Use multiple threads to calculate HyperLogLogPlusCounter in
> FactDistinctColumnsMapper
> -
>
> Key: KYLIN-2736
> URL: https://issues.apache.org/jira/browse/KYLIN-2736
> Project: Kylin
> Issue Type: Improvement
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
> Fix For: v2.3.0
>
> Attachments: APACHE-KYLIN-2736.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (KYLIN-3043) Don't need create materialized view for lookup tables without snapshot
[ https://issues.apache.org/jira/browse/KYLIN-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Li resolved KYLIN-3043. Resolution: Fixed merged to https://github.com/apache/kylin/commit/17838a19afb3891d6de7b5ac28dd61757a9e00f0 > Don't need create materialized view for lookup tables without snapshot > -- > > Key: KYLIN-3043 > URL: https://issues.apache.org/jira/browse/KYLIN-3043 > Project: Kylin > Issue Type: Improvement >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong > Fix For: v2.3.0 > > Attachments: APACHE-KYLIN-3043.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2736) Use multiple threads to calculate HyperLogLogPlusCounter in FactDistinctColumnsMapper
[ https://issues.apache.org/jira/browse/KYLIN-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong Yanghong updated KYLIN-2736: -- Attachment: APACHE-KYLIN-2736.patch > Use multiple threads to calculate HyperLogLogPlusCounter in > FactDistinctColumnsMapper > - > > Key: KYLIN-2736 > URL: https://issues.apache.org/jira/browse/KYLIN-2736 > Project: Kylin > Issue Type: Improvement >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong > Fix For: v2.3.0 > > Attachments: APACHE-KYLIN-2736.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2866) Enlarge the reducer number for hyperloglog statistics calculation at step FactDistinctColumnsJob
[ https://issues.apache.org/jira/browse/KYLIN-2866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong Yanghong updated KYLIN-2866: -- Attachment: APACHE-KYLIN-2866.patch > Enlarge the reducer number for hyperloglog statistics calculation at step > FactDistinctColumnsJob > > > Key: KYLIN-2866 > URL: https://issues.apache.org/jira/browse/KYLIN-2866 > Project: Kylin > Issue Type: Improvement > Components: Job Engine >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong > Fix For: v2.3.0 > > Attachments: APACHE-KYLIN-2866.patch > > > Currently only one reducer is assigned for hll stats calculation, which may > become the bottleneck for slow down this step. Since the stats for different > cuboids will not influence each other, it's better to divide the cuboid set > into several and assign a reduce for each subset. > The strategy of this patch is to assign 100 cuboids into a subset. And > there's a upper limit of reducers for hll stats calculation. Currently it's > 50. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2867) split large fuzzy Key set
[ https://issues.apache.org/jira/browse/KYLIN-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong Yanghong updated KYLIN-2867: -- Attachment: APACHE-KYLIN-2867.patch > split large fuzzy Key set > - > > Key: KYLIN-2867 > URL: https://issues.apache.org/jira/browse/KYLIN-2867 > Project: Kylin > Issue Type: Improvement > Components: Query Engine >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong > Attachments: APACHE-KYLIN-2867.patch > > > Too many fuzzy keys in one scan may downgrade the performance. Currently if > the number of fuzzy keys exceeds a threshold, like 200, the scan will not use > fuzzy key. However, this may also downgrade the performance. > There are many cases in eBay that the total number of fuzzy keys is around > 1000. To deal with these cases, it's better to split the large fuzzy key set, > like 5*200. Then for each subset, assign a scan. This strategy will increase > the number of scan to reduce the number of fuzzy keys in each scan to improve > the total performance. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2867) split large fuzzy Key set
[
https://issues.apache.org/jira/browse/KYLIN-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285506#comment-16285506
]
Zhong Yanghong commented on KYLIN-2867:
---
We can enable this feature by setting
{{kylin.storage.hbase.max-fuzzykey-scan-split}} to a number larger than 1
> split large fuzzy Key set
> -
>
> Key: KYLIN-2867
> URL: https://issues.apache.org/jira/browse/KYLIN-2867
> Project: Kylin
> Issue Type: Improvement
> Components: Query Engine
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>
> Too many fuzzy keys in one scan may downgrade the performance. Currently if
> the number of fuzzy keys exceeds a threshold, like 200, the scan will not use
> fuzzy key. However, this may also downgrade the performance.
> There are many cases in eBay that the total number of fuzzy keys is around
> 1000. To deal with these cases, it's better to split the large fuzzy key set,
> like 5*200. Then for each subset, assign a scan. This strategy will increase
> the number of scan to reduce the number of fuzzy keys in each scan to improve
> the total performance.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (KYLIN-3096) Upgrade Spark Version to 2.2.0
Ted Yu created KYLIN-3096: - Summary: Upgrade Spark Version to 2.2.0 Key: KYLIN-3096 URL: https://issues.apache.org/jira/browse/KYLIN-3096 Project: Kylin Issue Type: Bug Reporter: Ted Yu Priority: Minor Upgrade Spark Version from 2.1.2 to 2.2.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-3092) Synchronize read/write operations on Managers
[ https://issues.apache.org/jira/browse/KYLIN-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285489#comment-16285489 ] liyang commented on KYLIN-3092: --- fix done, pending merge master > Synchronize read/write operations on Managers > - > > Key: KYLIN-3092 > URL: https://issues.apache.org/jira/browse/KYLIN-3092 > Project: Kylin > Issue Type: Improvement >Reporter: liyang > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-3090) Refactor to consolidate all caches and managers under KylinConfig
[ https://issues.apache.org/jira/browse/KYLIN-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285487#comment-16285487 ] liyang commented on KYLIN-3090: --- fix done, pending merge master > Refactor to consolidate all caches and managers under KylinConfig > - > > Key: KYLIN-3090 > URL: https://issues.apache.org/jira/browse/KYLIN-3090 > Project: Kylin > Issue Type: Improvement >Reporter: liyang > > Refactor to consolidate all caches and managers under KylinConfig. > Such that there is a single place to clear (and GC) all cache under a > KylinConfig. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-3022) Add clone() for ISegment, which is needed when updating cube segment
[ https://issues.apache.org/jira/browse/KYLIN-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong Yanghong updated KYLIN-3022: -- Attachment: APACHE-KYLIN-3022.patch > Add clone() for ISegment, which is needed when updating cube segment > > > Key: KYLIN-3022 > URL: https://issues.apache.org/jira/browse/KYLIN-3022 > Project: Kylin > Issue Type: Improvement >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong > Attachments: APACHE-KYLIN-3022.patch > > > We should not update the memory state until the storage state is updated. > Otherwise when it fails to update the storage state, inconsistency issue will > occur. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-3004) Delete cube segment validation
[
https://issues.apache.org/jira/browse/KYLIN-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pan, Julian updated KYLIN-3004:
---
Attachment: KYLIN_3004.patch
Thanks, [~Shaofengshi]. Here is the new patch.
> Delete cube segment validation
> --
>
> Key: KYLIN-3004
> URL: https://issues.apache.org/jira/browse/KYLIN-3004
> Project: Kylin
> Issue Type: Bug
> Components: REST Service
>Affects Versions: v2.1.0
>Reporter: Pan, Julian
>Assignee: Pan, Julian
> Attachments: KYLIN_3004.patch, KYLIN_3004.patch
>
>
> In version 2.1, kylin allow hole between segment.
> But currently, there is validation for delete segment.
> Here is the code in CubeService:
> if (!segmentName.equals(cube.getSegments().get(0).getName())
> &&
> !segmentName.equals(cube.getSegments().get(cube.getSegments().size() -
> 1).getName())) {
> throw new
> BadRequestException(String.format(msg.getDELETE_NOT_FIRST_LAST_SEG(),
> segmentName));
> }
> Does it make sense? Should we remove the limit?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KYLIN-3022) Add clone() for ISegment, which is needed when updating cube segment
[ https://issues.apache.org/jira/browse/KYLIN-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong Yanghong updated KYLIN-3022: -- Description: We should not update the memory state until the storage state is updated. Otherwise when it fails to update the storage state, inconsistency issue will occur. > Add clone() for ISegment, which is needed when updating cube segment > > > Key: KYLIN-3022 > URL: https://issues.apache.org/jira/browse/KYLIN-3022 > Project: Kylin > Issue Type: Improvement >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong > > We should not update the memory state until the storage state is updated. > Otherwise when it fails to update the storage state, inconsistency issue will > occur. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (KYLIN-2986) Segments overlap issue may happen when concurrent merge or build
[
https://issues.apache.org/jira/browse/KYLIN-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285453#comment-16285453
]
Zhong Yanghong edited comment on KYLIN-2986 at 12/11/17 2:56 AM:
-
There're two issues.
# One is related to JIRA [KYLIN-3022 |
https://issues.apache.org/jira/browse/KYLIN-3022], we shouldn't change the
memory state of cube segment until the data is updated to database. Otherwise
when the concurrent issue happens, the state failed to update will lead to
[~yanghaogn]'s issue
# Another issue may relate to the concurrent issue among
{{calculateToBeSegments}} and {{updateCube}}. Current solution is to add a lock
for this block.
was (Author: yaho):
There're two issues.
# One is related to JIRA [KYLIN-3022 |
https://issues.apache.org/jira/browse/KYLIN-3022], we shouldn't change the
memory state of cube segment until the data is updated to database. Otherwise
when the concurrent issue happens, the state failed to update will lead to
[~yanghaogn]'s issue
> Segments overlap issue may happen when concurrent merge or build
>
>
> Key: KYLIN-2986
> URL: https://issues.apache.org/jira/browse/KYLIN-2986
> Project: Kylin
> Issue Type: Bug
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Trivial
> Labels: scope
> Attachments: APACHE-KYLIN-2986.patch, screenshot-1.png
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KYLIN-2986) Segments overlap issue may happen when concurrent merge or build
[ https://issues.apache.org/jira/browse/KYLIN-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong Yanghong updated KYLIN-2986: -- Attachment: APACHE-KYLIN-2986.patch > Segments overlap issue may happen when concurrent merge or build > > > Key: KYLIN-2986 > URL: https://issues.apache.org/jira/browse/KYLIN-2986 > Project: Kylin > Issue Type: Bug >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong >Priority: Trivial > Labels: scope > Attachments: APACHE-KYLIN-2986.patch, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (KYLIN-2986) Segments overlap issue may happen when concurrent merge or build
[ https://issues.apache.org/jira/browse/KYLIN-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285453#comment-16285453 ] Zhong Yanghong edited comment on KYLIN-2986 at 12/11/17 2:52 AM: - There're two issues. # One is related to JIRA [KYLIN-3022 | https://issues.apache.org/jira/browse/KYLIN-3022], we shouldn't change the memory state of cube segment until the data is updated to database. Otherwise when the concurrent issue happens, the state failed to update will lead to [~yanghaogn]'s issue was (Author: yaho): There're two issues. # One is related to JIRA [KYLIN-3022 | https://issues.apache.org/jira/browse/KYLIN-3022], we shouldn't change the memory state until the data is updated to database. > Segments overlap issue may happen when concurrent merge or build > > > Key: KYLIN-2986 > URL: https://issues.apache.org/jira/browse/KYLIN-2986 > Project: Kylin > Issue Type: Bug >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong >Priority: Trivial > Labels: scope > Attachments: screenshot-1.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2939) Get config properties not correct in UI
[
https://issues.apache.org/jira/browse/KYLIN-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285455#comment-16285455
]
Zhixiong Chen commented on KYLIN-2939:
--
I think there is no problem with the old code.
Could you show more detail about it ?
> Get config properties not correct in UI
> ---
>
> Key: KYLIN-2939
> URL: https://issues.apache.org/jira/browse/KYLIN-2939
> Project: Kylin
> Issue Type: Bug
> Components: Web
>Reporter: Pan, Julian
>Assignee: Pan, Julian
>Priority: Critical
> Attachments: KYLIN_2939.patch
>
>
> When I want to get kylin.env by getDeployEnv(), it will return
> kylin.env.hdfs-working-dir value. There is a bug in getProperty in
> kylinProperties.js.
> This function will return first properties will contains this name.
> Here is the fix:
> this.getProperty = function (name) {
> var keyIndex = _config.indexOf('\n' + name + '=');
> var keyLength = name.length;
> var partialResult = _config.substr(keyIndex);
> var preValueIndex = partialResult.indexOf("=");
> var sufValueIndex = partialResult.indexOf("\n", 2);
> return partialResult.substring(preValueIndex + 1, sufValueIndex);
> }
> If necessary, I can create a patch for it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Issue Comment Deleted] (KYLIN-2939) Get config properties not correct in UI
[
https://issues.apache.org/jira/browse/KYLIN-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhixiong Chen updated KYLIN-2939:
-
Comment: was deleted
(was: I think the code is right.)
> Get config properties not correct in UI
> ---
>
> Key: KYLIN-2939
> URL: https://issues.apache.org/jira/browse/KYLIN-2939
> Project: Kylin
> Issue Type: Bug
> Components: Web
>Reporter: Pan, Julian
>Assignee: Pan, Julian
>Priority: Critical
> Attachments: KYLIN_2939.patch
>
>
> When I want to get kylin.env by getDeployEnv(), it will return
> kylin.env.hdfs-working-dir value. There is a bug in getProperty in
> kylinProperties.js.
> This function will return first properties will contains this name.
> Here is the fix:
> this.getProperty = function (name) {
> var keyIndex = _config.indexOf('\n' + name + '=');
> var keyLength = name.length;
> var partialResult = _config.substr(keyIndex);
> var preValueIndex = partialResult.indexOf("=");
> var sufValueIndex = partialResult.indexOf("\n", 2);
> return partialResult.substring(preValueIndex + 1, sufValueIndex);
> }
> If necessary, I can create a patch for it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KYLIN-2986) Segments overlap issue may happen when concurrent merge or build
[ https://issues.apache.org/jira/browse/KYLIN-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285453#comment-16285453 ] Zhong Yanghong commented on KYLIN-2986: --- There're two issues. # One is related to JIRA [KYLIN-3022 | https://issues.apache.org/jira/browse/KYLIN-3022], we shouldn't change the memory state until the data is updated to database. > Segments overlap issue may happen when concurrent merge or build > > > Key: KYLIN-2986 > URL: https://issues.apache.org/jira/browse/KYLIN-2986 > Project: Kylin > Issue Type: Bug >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong >Priority: Trivial > Labels: scope > Attachments: APACHE-KYLIN-2986.patch, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2986) Segments overlap issue may happen when concurrent merge or build
[ https://issues.apache.org/jira/browse/KYLIN-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong Yanghong updated KYLIN-2986: -- Attachment: (was: APACHE-KYLIN-2986.patch) > Segments overlap issue may happen when concurrent merge or build > > > Key: KYLIN-2986 > URL: https://issues.apache.org/jira/browse/KYLIN-2986 > Project: Kylin > Issue Type: Bug >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong >Priority: Trivial > Labels: scope > Attachments: screenshot-1.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2953) List readable project not correct if add limit and offset
[ https://issues.apache.org/jira/browse/KYLIN-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285451#comment-16285451 ] Pan, Julian commented on KYLIN-2953: Thanks a lot, [~Shaofengshi] > List readable project not correct if add limit and offset > - > > Key: KYLIN-2953 > URL: https://issues.apache.org/jira/browse/KYLIN-2953 > Project: Kylin > Issue Type: Bug > Components: REST Service >Affects Versions: v2.1.0 >Reporter: Pan, Julian >Assignee: Pan, Julian > Fix For: v2.3.0 > > Attachments: KYLIN_2953.patch > > > There is one line getReadableProjects in ProjectController: > List projectInstances = > projectService.listAllProjects(limit, offset); > That means just the part of projects, then validate the ACL. > If user's project beyond the limit, then he will never get the projects if he > put limit and offset. > It should be similar with cube list, get all the projects then validate the > ACL, at last get the sub list by limit and offset. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2959) SAML logout issue
[ https://issues.apache.org/jira/browse/KYLIN-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285452#comment-16285452 ] Pan, Julian commented on KYLIN-2959: Thanks a lot, [~Shaofengshi] > SAML logout issue > - > > Key: KYLIN-2959 > URL: https://issues.apache.org/jira/browse/KYLIN-2959 > Project: Kylin > Issue Type: Bug > Components: REST Service, Web >Reporter: Pan, Julian >Assignee: Pan, Julian >Priority: Minor > Fix For: v2.3.0 > > Attachments: KYLIN_2959.patch > > > When user click logout in portal, which will cause this issue for SAML mode. > User can not logout successful, the session did not disconnect and still user > can see the menu. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2940) List job restful throw NPE when time filter not set
[
https://issues.apache.org/jira/browse/KYLIN-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285450#comment-16285450
]
Pan, Julian commented on KYLIN-2940:
Thanks a lot, [~Shaofengshi]
> List job restful throw NPE when time filter not set
> ---
>
> Key: KYLIN-2940
> URL: https://issues.apache.org/jira/browse/KYLIN-2940
> Project: Kylin
> Issue Type: Improvement
> Components: REST Service
>Affects Versions: v2.1.0
>Reporter: Pan, Julian
>Assignee: Pan, Julian
> Fix For: v2.3.0
>
> Attachments: KYLIN_2940.patch
>
>
> Here is the error response:
> {"code":"999","data":null,"msg":null,"stacktrace":"java.lang.NullPointerException\n\tat
>
> org.apache.kylin.rest.controller.JobController.list(JobController.java:72)\n\tat
> sun.reflect.GeneratedMethodAccessor283.invoke(Unknown Source)\n\tat
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
> java.lang.reflect.Method.invoke(Method.java:606)\n\tat
> org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:221)\n\tat
>
> org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:136)\n\tat
>
> org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:110)\n\tat
>
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:832)\n\tat
>
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:743)\n\tat
>
> org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)\n\tat
>
> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:961)\n\tat
>
> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:895)\n\tat
>
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:967)\n\tat
>
> org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:858)\n\tat
> javax.servlet.http.HttpServlet.service(HttpServlet.java:624)\n\tat
> org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:843)\n\tat
> javax.servlet.http.HttpServlet.service(HttpServlet.java:731)\n\tat
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)\n\tat
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)\n\tat
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)\n\tat
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)\n\tat
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)\n\tat
>
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:316)\n\tat
>
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:126)\n\tat
>
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:90)\n\tat
>
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)\n\tat
>
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:114)\n\tat
>
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)\n\tat
>
> org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:122)\n\tat
>
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)\n\tat
>
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:111)\n\tat
>
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)\n\tat
>
> org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:169)\n\tat
>
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)\n\tat
>
> org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:48)\n\tat
>
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)\n\tat
>
>
[jira] [Resolved] (KYLIN-3062) Hide RAW measure
[ https://issues.apache.org/jira/browse/KYLIN-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen resolved KYLIN-3062. -- Resolution: Fixed > Hide RAW measure > > > Key: KYLIN-3062 > URL: https://issues.apache.org/jira/browse/KYLIN-3062 > Project: Kylin > Issue Type: Task > Components: Web >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Fix For: v2.3.0 > > Attachments: KYLIN-3062-2.patch, KYLIN-3062.patch > > > See the discussion here: > http://apache-kylin.74782.x6.nabble.com/Discuss-Disable-hide-quot-RAW-quot-measure-in-Kylin-web-GUI-td6636.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-3062) Hide RAW measure
[ https://issues.apache.org/jira/browse/KYLIN-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285449#comment-16285449 ] Zhixiong Chen commented on KYLIN-3062: -- OK.Thanks! > Hide RAW measure > > > Key: KYLIN-3062 > URL: https://issues.apache.org/jira/browse/KYLIN-3062 > Project: Kylin > Issue Type: Task > Components: Web >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Fix For: v2.3.0 > > Attachments: KYLIN-3062-2.patch, KYLIN-3062.patch > > > See the discussion here: > http://apache-kylin.74782.x6.nabble.com/Discuss-Disable-hide-quot-RAW-quot-measure-in-Kylin-web-GUI-td6636.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2882) Disable datepicker input avoid user typing issue
[ https://issues.apache.org/jira/browse/KYLIN-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285448#comment-16285448 ] Pan, Julian commented on KYLIN-2882: OK, maybe we need find a better way to validation. > Disable datepicker input avoid user typing issue > > > Key: KYLIN-2882 > URL: https://issues.apache.org/jira/browse/KYLIN-2882 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Pan, Julian >Assignee: Pan, Julian >Priority: Minor > > When user typing in input for datepicker, which will cause date error issue. > Could we add the attribute read-only for datepicker input? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2875) Cube e-mail notification Validation
[ https://issues.apache.org/jira/browse/KYLIN-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285447#comment-16285447 ] Pan, Julian commented on KYLIN-2875: Thanks a lot, [~Shaofengshi] > Cube e-mail notification Validation > --- > > Key: KYLIN-2875 > URL: https://issues.apache.org/jira/browse/KYLIN-2875 > Project: Kylin > Issue Type: Improvement > Components: REST Service, Web >Reporter: Pan, Julian >Assignee: Pan, Julian > Fix For: v2.3.0 > > Attachments: KYLIN_2875.patch > > > Validation e-mail notification list avoid EmailException: > 2017-03-28 20:01:56,453 INFO [pool-10-thread-8] > execution.AbstractExecutable:250 : notify > list:[us...@apache.com;us...@apache.com;, dl-user-gr...@apache.com] > 2017-03-28 20:01:56,453 ERROR [pool-10-thread-8] util.MailService:112 : > Illegal semicolon, not in group > org.apache.commons.mail.EmailException: Illegal semicolon, not in group > at org.apache.commons.mail.Email.createInternetAddress(Email.java:541) > at org.apache.commons.mail.Email.addTo(Email.java:653) > at org.apache.commons.mail.Email.addTo(Email.java:636) > at org.apache.commons.mail.Email.addTo(Email.java:618) > at org.apache.kylin.common.util.MailService.sendMail(MailService.java:97) > at org.apache.kylin.common.util.MailService.sendMail(MailService.java:70) > at > org.apache.kylin.job.execution.AbstractExecutable.notifyUserStatusChange(AbstractExecutable.java:251) > at > org.apache.kylin.job.execution.DefaultChainedExecutable.onStatusChange(DefaultChainedExecutable.java:105) > at org.apache.kylin.engine.mr.CubingJob.onStatusChange(CubingJob.java:296) > at > org.apache.kylin.job.execution.DefaultChainedExecutable.onExecuteFinished(DefaultChainedExecutable.java:89) > at org.apache.kylin.engine.mr.CubingJob.onExecuteFinished(CubingJob.java:292) > at > org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:135) > at > org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:133) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: javax.mail.internet.AddressException: Illegal semicolon, not in > group in string > ``cais...@ebay.com;kalagupack...@ebay.com;cb...@ebay.com;cb...@ebay.com;'' at > position 16 > at javax.mail.internet.InternetAddress.parse(InternetAddress.java:780) > at javax.mail.internet.InternetAddress.parse(InternetAddress.java:555) > at javax.mail.internet.InternetAddress.(InternetAddress.java:91) > at org.apache.commons.mail.Email.createInternetAddress(Email.java:514) > ... 15 more -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2941) Configuration setting for SSO
[
https://issues.apache.org/jira/browse/KYLIN-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285445#comment-16285445
]
Pan, Julian commented on KYLIN-2941:
I'm not sure, whether the document describe kylin.properties?
I add a attribute(kylin.security.saml.keystore-file) in kylin.properties for
key store file path instead of kylinSecurity.xml directly.
> Configuration setting for SSO
> -
>
> Key: KYLIN-2941
> URL: https://issues.apache.org/jira/browse/KYLIN-2941
> Project: Kylin
> Issue Type: Improvement
>Reporter: Pan, Julian
>Assignee: Pan, Julian
>Priority: Minor
> Fix For: v2.3.0
>
> Attachments: KYLIN_2941.patch
>
>
> I noticed there is kylin.security.saml.metadata-file properties in
> kylin.properties but never used.
> And there are classpath:samlKeystore.jks & sso_metadata.xml the configuration
> in kylinSecurity.xml.
> Could we config both of them in kylin.properties?
> And change them in kylinSecurity.xml. e.g ${kylin.security.saml.metadata-file}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KYLIN-2986) Segments overlap issue may happen when concurrent merge or build
[ https://issues.apache.org/jira/browse/KYLIN-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong Yanghong updated KYLIN-2986: -- Attachment: APACHE-KYLIN-2986.patch > Segments overlap issue may happen when concurrent merge or build > > > Key: KYLIN-2986 > URL: https://issues.apache.org/jira/browse/KYLIN-2986 > Project: Kylin > Issue Type: Bug >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong >Priority: Trivial > Labels: scope > Attachments: APACHE-KYLIN-2986.patch, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2690) Upgrade calcite to release 1.15
[ https://issues.apache.org/jira/browse/KYLIN-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KYLIN-2690: -- Summary: Upgrade calcite to release 1.15 (was: Upgrade calcite to release 1.14) > Upgrade calcite to release 1.15 > --- > > Key: KYLIN-2690 > URL: https://issues.apache.org/jira/browse/KYLIN-2690 > Project: Kylin > Issue Type: Improvement >Reporter: Ted Yu > > Calcite 1.14 has released. > We should consider upgrading to this release. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2690) Upgrade calcite to release 1.15
[ https://issues.apache.org/jira/browse/KYLIN-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KYLIN-2690: -- Description: Calcite 1.15 has released. We should consider upgrading to this release. was: Calcite 1.14 has released. We should consider upgrading to this release. > Upgrade calcite to release 1.15 > --- > > Key: KYLIN-2690 > URL: https://issues.apache.org/jira/browse/KYLIN-2690 > Project: Kylin > Issue Type: Improvement >Reporter: Ted Yu > > Calcite 1.15 has released. > We should consider upgrading to this release. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-3094) Upgrade zookeeper to 3.4.11
[ https://issues.apache.org/jira/browse/KYLIN-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KYLIN-3094: -- Description: Current zookeeper release is 3.4.11 We should upgrade dependency from 3.4.8 to 3.4.11 where there is important security fix. One such critical fix is ZOOKEEPER-2146, which can be explored maliciously was: Current zookeeper release is 3.4.11 We should upgrade dependency from 3.4.8 to 3.4.11 where there is important security fix. > Upgrade zookeeper to 3.4.11 > --- > > Key: KYLIN-3094 > URL: https://issues.apache.org/jira/browse/KYLIN-3094 > Project: Kylin > Issue Type: Improvement >Reporter: Ted Yu >Priority: Minor > > Current zookeeper release is 3.4.11 > We should upgrade dependency from 3.4.8 to 3.4.11 where there is important > security fix. > One such critical fix is ZOOKEEPER-2146, which can be explored maliciously -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-3093) Upgrade curator to 2.10.0
[ https://issues.apache.org/jira/browse/KYLIN-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285281#comment-16285281 ] Billy Liu commented on KYLIN-3093: -- Hi [~Aron.tao], could you take care this issue? > Upgrade curator to 2.10.0 > - > > Key: KYLIN-3093 > URL: https://issues.apache.org/jira/browse/KYLIN-3093 > Project: Kylin > Issue Type: Improvement >Reporter: Ted Yu > > curator-2.10.0 has several bug fixes over current version (2.7.1), updating > would help improve stability. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-3094) Upgrade zookeeper to 3.4.11
[ https://issues.apache.org/jira/browse/KYLIN-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285280#comment-16285280 ] Billy Liu commented on KYLIN-3094: -- Kylin does not release ZooKeeper. ZooKeeper is from Hadoop distribution. > Upgrade zookeeper to 3.4.11 > --- > > Key: KYLIN-3094 > URL: https://issues.apache.org/jira/browse/KYLIN-3094 > Project: Kylin > Issue Type: Improvement >Reporter: Ted Yu >Priority: Minor > > Current zookeeper release is 3.4.11 > We should upgrade dependency from 3.4.8 to 3.4.11 where there is important > security fix. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
