[jira] [Comment Edited] (KYLIN-3668) Performing a cube build error on the Chinese hive table field
[ https://issues.apache.org/jira/browse/KYLIN-3668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698448#comment-16698448 ] Yichen Zhou edited comment on KYLIN-3668 at 11/26/18 3:36 AM: -- Hi [~wxs] , As far as I know, hive doesn't support UTF-8 for database/table/column name yet. [https://cwiki.apache.org/confluence/display/Hive/User+FAQ#UserFAQ-DoesHivesupportUnicode?] This is because hive needs to pass the meta information between components, sometimes as XML sometimes as json, and these serializations are not able to deal with complex encoding. There are some difficulties to support Chinese character names in Kylin and we have no plan to do this so far. Maybe table/column comments can be an alternative for you. was (Author: yichen.zhou): Hi [~wxs] , As far as I know, hive doesn't support UTF-8 for database/table/column name yet. [https://cwiki.apache.org/confluence/display/Hive/User+FAQ#UserFAQ-DoesHivesupportUnicode?] This is because hive needs to pass the meta information between components, sometimes as XML sometimes as json, and these serializations are not able to deal with complex encoding. It is complex to support Chinese character names in Kylin and we have no plan to do this so far. Maybe table/column comments can be an alternative for you. > Performing a cube build error on the Chinese hive table field > - > > Key: KYLIN-3668 > URL: https://issues.apache.org/jira/browse/KYLIN-3668 > Project: Kylin > Issue Type: Bug > Components: Tools, Build and Test >Affects Versions: all > Environment: KYLIN Version2.3 hbase1.2.6 hive1.2.2 >Reporter: wxs >Assignee: Yichen Zhou >Priority: Major > Fix For: v2.6.0 > > > The Chinese name can be created in hive, and the field name can be named > Chinese characters. Easy to understand and remember. > The Chinese table of DataSource load hive in KYLIN is displayed normally. But > when you do cube build, the first step: create intermediate flat hive table > error. > KYLIN advantage can be connected to BI tools, field Chinese, for the > presentation layer is the highlights and concerns. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (KYLIN-3668) Performing a cube build error on the Chinese hive table field
[ https://issues.apache.org/jira/browse/KYLIN-3668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698448#comment-16698448 ] Yichen Zhou edited comment on KYLIN-3668 at 11/26/18 3:35 AM: -- Hi [~wxs] , As far as I know, hive doesn't support UTF-8 for database/table/column name yet. [https://cwiki.apache.org/confluence/display/Hive/User+FAQ#UserFAQ-DoesHivesupportUnicode?] This is because hive needs to pass the meta information between components, sometimes as XML sometimes as json, and these serializations are not able to deal with complex encoding. It is complex to support Chinese character names in Kylin and we have no plan to do this so far. Maybe table/column comments can be an alternative for you. was (Author: yichen.zhou): Hi [~wxs] , As far as I know, hive doesn't support UTF-8 for database/table/column name yet. [https://cwiki.apache.org/confluence/display/Hive/User+FAQ#UserFAQ-DoesHivesupportUnicode?] This is because hive needs to pass this meta information between components, sometimes as XML sometimes as json, and these serializations are not able to deal with complex encoding. It is complex to support Chinese character names in Kylin and we have no plan to do this so far. Maybe table/column comments can be an alternative for you. > Performing a cube build error on the Chinese hive table field > - > > Key: KYLIN-3668 > URL: https://issues.apache.org/jira/browse/KYLIN-3668 > Project: Kylin > Issue Type: Bug > Components: Tools, Build and Test >Affects Versions: all > Environment: KYLIN Version2.3 hbase1.2.6 hive1.2.2 >Reporter: wxs >Assignee: Yichen Zhou >Priority: Major > Fix For: v2.6.0 > > > The Chinese name can be created in hive, and the field name can be named > Chinese characters. Easy to understand and remember. > The Chinese table of DataSource load hive in KYLIN is displayed normally. But > when you do cube build, the first step: create intermediate flat hive table > error. > KYLIN advantage can be connected to BI tools, field Chinese, for the > presentation layer is the highlights and concerns. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3668) Performing a cube build error on the Chinese hive table field
[ https://issues.apache.org/jira/browse/KYLIN-3668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698448#comment-16698448 ] Yichen Zhou commented on KYLIN-3668: Hi [~wxs] , As far as I know, hive doesn't support UTF-8 for database/table/column name yet. [https://cwiki.apache.org/confluence/display/Hive/User+FAQ#UserFAQ-DoesHivesupportUnicode?] This is because hive needs to pass this meta information between components, sometimes as XML sometimes as json, and these serializations are not able to deal with complex encoding. It is complex to support Chinese character names in Kylin and we have no plan to do this so far. Maybe table/column comments can be an alternative for you. > Performing a cube build error on the Chinese hive table field > - > > Key: KYLIN-3668 > URL: https://issues.apache.org/jira/browse/KYLIN-3668 > Project: Kylin > Issue Type: Bug > Components: Tools, Build and Test >Affects Versions: all > Environment: KYLIN Version2.3 hbase1.2.6 hive1.2.2 >Reporter: wxs >Assignee: Yichen Zhou >Priority: Major > Fix For: v2.6.0 > > > The Chinese name can be created in hive, and the field name can be named > Chinese characters. Easy to understand and remember. > The Chinese table of DataSource load hive in KYLIN is displayed normally. But > when you do cube build, the first step: create intermediate flat hive table > error. > KYLIN advantage can be connected to BI tools, field Chinese, for the > presentation layer is the highlights and concerns. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3668) Performing a cube build error on the Chinese hive table field
[ https://issues.apache.org/jira/browse/KYLIN-3668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697073#comment-16697073 ] Yichen Zhou commented on KYLIN-3668: Hi [~wxs] , how did you create tables with Chinese fields in hive? I tried to create tables in hive shell but failed. So I created an English table and then changed the hive metadata in mysql by Sequel Pro. Finally, I get a table with Chinese field names, but I still cannot execute the sql contains Chinese characters in hive shell. > Performing a cube build error on the Chinese hive table field > - > > Key: KYLIN-3668 > URL: https://issues.apache.org/jira/browse/KYLIN-3668 > Project: Kylin > Issue Type: Bug > Components: Tools, Build and Test >Affects Versions: all > Environment: KYLIN Version2.3 hbase1.2.6 hive1.2.2 >Reporter: wxs >Assignee: Yichen Zhou >Priority: Major > Fix For: v2.6.0 > > > The Chinese name can be created in hive, and the field name can be named > Chinese characters. Easy to understand and remember. > The Chinese table of DataSource load hive in KYLIN is displayed normally. But > when you do cube build, the first step: create intermediate flat hive table > error. > KYLIN advantage can be connected to BI tools, field Chinese, for the > presentation layer is the highlights and concerns. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3673) Increase smoke-test cube building time
Yichen Zhou created KYLIN-3673: -- Summary: Increase smoke-test cube building time Key: KYLIN-3673 URL: https://issues.apache.org/jira/browse/KYLIN-3673 Project: Kylin Issue Type: Test Components: Tools, Build and Test Affects Versions: v2.5.0 Reporter: Yichen Zhou Assignee: Yichen Zhou In smoke-test, cube building job which costs more than 20 mins will be treated as failure. This time is too short in some cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3673) Increasing the limit of smoke-test building time
[ https://issues.apache.org/jira/browse/KYLIN-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yichen Zhou updated KYLIN-3673: --- Summary: Increasing the limit of smoke-test building time (was: Increase smoke-test cube building time) > Increasing the limit of smoke-test building time > > > Key: KYLIN-3673 > URL: https://issues.apache.org/jira/browse/KYLIN-3673 > Project: Kylin > Issue Type: Test > Components: Tools, Build and Test >Affects Versions: v2.5.0 >Reporter: Yichen Zhou >Assignee: Yichen Zhou >Priority: Minor > > In smoke-test, cube building job which costs more than 20 mins will be > treated as failure. > This time is too short in some cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3439) configuration "kylin.web.timezone" is Inconsistent between kylin-defaults.properties and KylinConfigBase.java
[ https://issues.apache.org/jira/browse/KYLIN-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669717#comment-16669717 ] Yichen Zhou commented on KYLIN-3439: I have verified this and it works now. > configuration "kylin.web.timezone" is Inconsistent between > kylin-defaults.properties and KylinConfigBase.java > -- > > Key: KYLIN-3439 > URL: https://issues.apache.org/jira/browse/KYLIN-3439 > Project: Kylin > Issue Type: Bug >Reporter: Jiatao Tao >Assignee: Jiatao Tao >Priority: Minor > Fix For: v2.6.0, v2.5.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3526) No check for hybrid name with special character
[ https://issues.apache.org/jira/browse/KYLIN-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669705#comment-16669705 ] Yichen Zhou commented on KYLIN-3526: I have verified this issue. It it fixed in 2.5.x > No check for hybrid name with special character > --- > > Key: KYLIN-3526 > URL: https://issues.apache.org/jira/browse/KYLIN-3526 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Na Zhai >Assignee: Roger >Priority: Minor > Fix For: v2.5.1 > > Attachments: 名称没做限制.png > > > When create hybrid，there is no check for hybrid name with special character. > Such as !@&. > Hybrid can be created successfully with name like hy! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3582) String comparison should not use == in RecordEvent
[
https://issues.apache.org/jira/browse/KYLIN-3582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668279#comment-16668279
]
Yichen Zhou commented on KYLIN-3582:
I verified this. It is fixed now.
> String comparison should not use == in RecordEvent
> --
>
> Key: KYLIN-3582
> URL: https://issues.apache.org/jira/browse/KYLIN-3582
> Project: Kylin
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: XiaoXiang Yu
>Priority: Minor
> Fix For: v2.4.2, v2.5.1
>
>
> Here is related code:
> {code}
> for (RecordReserveKeyEnum reserveKey :
> RecordReserveKeyEnum.values()) {
> if (reserveKey.reserveKey == key) {
> {code}
> equals() should be used to compare Strings.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3595) Beeline does not retrieve CLASSPATH and hangs
[ https://issues.apache.org/jira/browse/KYLIN-3595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668278#comment-16668278 ] Yichen Zhou commented on KYLIN-3595: I verified this. It works now. > Beeline does not retrieve CLASSPATH and hangs > - > > Key: KYLIN-3595 > URL: https://issues.apache.org/jira/browse/KYLIN-3595 > Project: Kylin > Issue Type: Bug > Components: Environment >Affects Versions: v2.5.0 >Reporter: Richard Jarvis >Assignee: Richard Jarvis >Priority: Minor > Fix For: v2.5.1 > > > There is no semi-colon at the end of the set command provided to the beeline > script in find-hive-dependency.sh. This causes the script to hang. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3297) sql在解析>大值 and <小值的时候，kylin出现内存溢出。
[
https://issues.apache.org/jira/browse/KYLIN-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16649768#comment-16649768
]
Yichen Zhou commented on KYLIN-3297:
Hi [~xer001], I didn't meet this issue when executing the following query for
sample cube.
{quote}select part_dt, trans_id from KYLIN_SALES where part_dt>='2012-09-09'
and part_dt<='2012-01-08';
{quote}
It returns 'No Result.', which is the correct answer.
Could you provide the kylin log or any other information so that I can
reproduce this issue?
> sql在解析>大值 and <小值的时候，kylin出现内存溢出。
> -
>
> Key: KYLIN-3297
> URL: https://issues.apache.org/jira/browse/KYLIN-3297
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Affects Versions: v2.2.0
> Environment: oracle linux 6.8
> cup 8C
> memory 48G
> apache kylin v2.2.0
>Reporter: 陈家宇
>Priority: Major
> Fix For: v2.6.0
>
>
> select f.plant_code,f.report_business_area,f.orderby,sum(f.a)a,
> case when sum(f.a)=0 then 0 else sum(f.qty)/sum(f.a) end zt from (
> select h.business_area_desc,h.plant_code,
> case when p.report_business_area like '%切大片%' then '切大片'
> else p.report_business_area end report_business_area,
> case when p.report_business_area like '%切大片%' then '00'
> else p.orderby end orderby,
> sum(p.quantity) qty,sum(a)a from pkn_kpi p
> inner join hcm_area h on p.plant_id=h.plant_id
> where 1=1
> and h.business_area_desc='上海'
> and h.plant_code='S1'
> and p.calendar_day>='2018-03-19'
> and p.calendar_day<='2018-03-18'
> and trim(p.report_business_area) is not null
> group by h.business_area_desc,h.plant_code,p.report_business_area,p.orderby
> ) f
> group by f.plant_code,f.report_business_area,f.orderby
> order by orderby
> 以上的calendar_day条件，顺序输入反了，变成calendar_day>大值 and
> calendar_day<小值，出现了kylin内存溢出，并且崩溃。正常这种情况是没有数据输出才对。
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3409) Write metric error when run a query.
[ https://issues.apache.org/jira/browse/KYLIN-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16647718#comment-16647718 ] Yichen Zhou commented on KYLIN-3409: Hi [~praveenece], thanks for reporting the issue. Can you provide your kylin version and what query did you execute? > Write metric error when run a query. > > > Key: KYLIN-3409 > URL: https://issues.apache.org/jira/browse/KYLIN-3409 > Project: Kylin > Issue Type: Bug >Reporter: praveenece >Priority: Major > Fix For: v2.6.0 > > > Hi, > I hit query(using sub query) against Cube the below exception is coming in > kylin log > but kylin UI response output. > why its coming? > 2018-06-13 17:15:51,153 WARN [Query 707b91e9-bcaa-46ef-be66-e7b74a3442d0-69] > service.QueryService:471 : Write metric error. > java.lang.NullPointerException > at > org.apache.kylin.rest.metrics.QueryMetricsFacade.updateMetricsToReservoir(QueryMetricsFacade.java:125) > at > org.apache.kylin.rest.metrics.QueryMetricsFacade.updateMetrics(QueryMetricsFacade.java:73) > at > org.apache.kylin.rest.service.QueryService.recordMetric(QueryService.java:560) > at > org.apache.kylin.rest.service.QueryService.doQueryWithCache(QueryService.java:469) > at > org.apache.kylin.rest.service.QueryService.doQueryWithCache(QueryService.java:390) > at > org.apache.kylin.rest.controller.QueryController.query(QueryController.java:86) > at sun.reflect.GeneratedMethodAccessor313.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:205) > at > org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:133) > at > org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:97) > at > org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:827) > at > org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:738) > at > org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85) > at > org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:967) > at > org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:901) > at > org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:970) > at > org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:872) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:650) > at > org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:731) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (KYLIN-3590) Missing argument to exception message String in ModelController
[
https://issues.apache.org/jira/browse/KYLIN-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yichen Zhou updated KYLIN-3590:
---
Comment: was deleted
(was: I will fix this.)
> Missing argument to exception message String in ModelController
> ---
>
> Key: KYLIN-3590
> URL: https://issues.apache.org/jira/browse/KYLIN-3590
> Project: Kylin
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yiming Liu
>Priority: Major
> Fix For: v2.5.1
>
>
> Here is related code:
> {code}
> String.format(Locale.ROOT,
> "Invalid model name %s, only letters, numbers and
> underscore " + "supported."),
> {code}
> There is no argument for '%s'
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KYLIN-3590) Missing argument to exception message String in ModelController
[
https://issues.apache.org/jira/browse/KYLIN-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yichen Zhou resolved KYLIN-3590.
Resolution: Fixed
Assignee: Yiming Liu (was: Yichen Zhou)
Fix Version/s: v2.5.1
Fixed by [https://github.com/apache/kylin/pull/270.] Already merged.
> Missing argument to exception message String in ModelController
> ---
>
> Key: KYLIN-3590
> URL: https://issues.apache.org/jira/browse/KYLIN-3590
> Project: Kylin
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yiming Liu
>Priority: Major
> Fix For: v2.5.1
>
>
> Here is related code:
> {code}
> String.format(Locale.ROOT,
> "Invalid model name %s, only letters, numbers and
> underscore " + "supported."),
> {code}
> There is no argument for '%s'
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KYLIN-3589) Different type is used to check presence in Collection in AclPermissionUtil
[
https://issues.apache.org/jira/browse/KYLIN-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yichen Zhou resolved KYLIN-3589.
Resolution: Fixed
Assignee: Yiming Liu (was: Yichen Zhou)
Fix Version/s: v2.6.0
> Different type is used to check presence in Collection in AclPermissionUtil
> ---
>
> Key: KYLIN-3589
> URL: https://issues.apache.org/jira/browse/KYLIN-3589
> Project: Kylin
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yiming Liu
>Priority: Major
> Fix For: v2.6.0
>
>
> Here is related code:
> {code}
> public static List transformAuthorities(Collection GrantedAuthority> authorities) {
> List ret = new ArrayList();
> for (GrantedAuthority auth : authorities) {
> if (!authorities.contains(auth.getAuthority())) {
> {code}
> auth.getAuthority() shouldn't be used to check presence in the Collection
> since it is not of GrantedAuthority type.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3589) Different type is used to check presence in Collection in AclPermissionUtil
[
https://issues.apache.org/jira/browse/KYLIN-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16633191#comment-16633191
]
Yichen Zhou commented on KYLIN-3589:
Fixed by [https://github.com/apache/kylin/pull/270.] Already merged.
> Different type is used to check presence in Collection in AclPermissionUtil
> ---
>
> Key: KYLIN-3589
> URL: https://issues.apache.org/jira/browse/KYLIN-3589
> Project: Kylin
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yichen Zhou
>Priority: Major
>
> Here is related code:
> {code}
> public static List transformAuthorities(Collection GrantedAuthority> authorities) {
> List ret = new ArrayList();
> for (GrantedAuthority auth : authorities) {
> if (!authorities.contains(auth.getAuthority())) {
> {code}
> auth.getAuthority() shouldn't be used to check presence in the Collection
> since it is not of GrantedAuthority type.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (KYLIN-3589) Different type is used to check presence in Collection in AclPermissionUtil
[
https://issues.apache.org/jira/browse/KYLIN-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yichen Zhou updated KYLIN-3589:
---
Comment: was deleted
(was: I will fix this.)
> Different type is used to check presence in Collection in AclPermissionUtil
> ---
>
> Key: KYLIN-3589
> URL: https://issues.apache.org/jira/browse/KYLIN-3589
> Project: Kylin
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yichen Zhou
>Priority: Major
>
> Here is related code:
> {code}
> public static List transformAuthorities(Collection GrantedAuthority> authorities) {
> List ret = new ArrayList();
> for (GrantedAuthority auth : authorities) {
> if (!authorities.contains(auth.getAuthority())) {
> {code}
> auth.getAuthority() shouldn't be used to check presence in the Collection
> since it is not of GrantedAuthority type.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KYLIN-3602) Enable more checkstyle rules
Yichen Zhou created KYLIN-3602: -- Summary: Enable more checkstyle rules Key: KYLIN-3602 URL: https://issues.apache.org/jira/browse/KYLIN-3602 Project: Kylin Issue Type: Improvement Components: Others Reporter: Yichen Zhou Fix For: v2.6.0 Attachments: checkstyle-aggregate.html The checkstyle rules of kylin is too weak. We need to reinfore them to achieve better code quality. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KYLIN-3587) Null value is used in IllegalStateException message
[
https://issues.apache.org/jira/browse/KYLIN-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yichen Zhou resolved KYLIN-3587.
Resolution: Fixed
> Null value is used in IllegalStateException message
> ---
>
> Key: KYLIN-3587
> URL: https://issues.apache.org/jira/browse/KYLIN-3587
> Project: Kylin
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yichen Zhou
>Priority: Minor
>
> In ProjectManager :
> {code}
> TableDesc table = metaMgr.getTableDesc(tableId, projectName);
> if (table == null) {
> throw new IllegalStateException("Cannot find table '" +
> table + "' in metadata manager");
> {code}
> Since table is null, the exception message is not helpful.
> It seems including tableId in the message is better.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3589) Different type is used to check presence in Collection in AclPermissionUtil
[
https://issues.apache.org/jira/browse/KYLIN-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16626656#comment-16626656
]
Yichen Zhou commented on KYLIN-3589:
I will fix this.
> Different type is used to check presence in Collection in AclPermissionUtil
> ---
>
> Key: KYLIN-3589
> URL: https://issues.apache.org/jira/browse/KYLIN-3589
> Project: Kylin
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yichen Zhou
>Priority: Major
>
> Here is related code:
> {code}
> public static List transformAuthorities(Collection GrantedAuthority> authorities) {
> List ret = new ArrayList();
> for (GrantedAuthority auth : authorities) {
> if (!authorities.contains(auth.getAuthority())) {
> {code}
> auth.getAuthority() shouldn't be used to check presence in the Collection
> since it is not of GrantedAuthority type.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3590) Missing argument to exception message String in ModelController
[
https://issues.apache.org/jira/browse/KYLIN-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16626655#comment-16626655
]
Yichen Zhou commented on KYLIN-3590:
I will fix this.
> Missing argument to exception message String in ModelController
> ---
>
> Key: KYLIN-3590
> URL: https://issues.apache.org/jira/browse/KYLIN-3590
> Project: Kylin
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Major
>
> Here is related code:
> {code}
> String.format(Locale.ROOT,
> "Invalid model name %s, only letters, numbers and
> underscore " + "supported."),
> {code}
> There is no argument for '%s'
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (KYLIN-3590) Missing argument to exception message String in ModelController
[
https://issues.apache.org/jira/browse/KYLIN-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yichen Zhou reassigned KYLIN-3590:
--
Assignee: Yichen Zhou
> Missing argument to exception message String in ModelController
> ---
>
> Key: KYLIN-3590
> URL: https://issues.apache.org/jira/browse/KYLIN-3590
> Project: Kylin
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yichen Zhou
>Priority: Major
>
> Here is related code:
> {code}
> String.format(Locale.ROOT,
> "Invalid model name %s, only letters, numbers and
> underscore " + "supported."),
> {code}
> There is no argument for '%s'
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (KYLIN-3589) Different type is used to check presence in Collection in AclPermissionUtil
[
https://issues.apache.org/jira/browse/KYLIN-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yichen Zhou reassigned KYLIN-3589:
--
Assignee: Yichen Zhou
> Different type is used to check presence in Collection in AclPermissionUtil
> ---
>
> Key: KYLIN-3589
> URL: https://issues.apache.org/jira/browse/KYLIN-3589
> Project: Kylin
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yichen Zhou
>Priority: Major
>
> Here is related code:
> {code}
> public static List transformAuthorities(Collection GrantedAuthority> authorities) {
> List ret = new ArrayList();
> for (GrantedAuthority auth : authorities) {
> if (!authorities.contains(auth.getAuthority())) {
> {code}
> auth.getAuthority() shouldn't be used to check presence in the Collection
> since it is not of GrantedAuthority type.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3587) Null value is used in IllegalStateException message
[
https://issues.apache.org/jira/browse/KYLIN-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16626654#comment-16626654
]
Yichen Zhou commented on KYLIN-3587:
I will fix this.
> Null value is used in IllegalStateException message
> ---
>
> Key: KYLIN-3587
> URL: https://issues.apache.org/jira/browse/KYLIN-3587
> Project: Kylin
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yichen Zhou
>Priority: Minor
>
> In ProjectManager :
> {code}
> TableDesc table = metaMgr.getTableDesc(tableId, projectName);
> if (table == null) {
> throw new IllegalStateException("Cannot find table '" +
> table + "' in metadata manager");
> {code}
> Since table is null, the exception message is not helpful.
> It seems including tableId in the message is better.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (KYLIN-3587) Null value is used in IllegalStateException message
[
https://issues.apache.org/jira/browse/KYLIN-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yichen Zhou reassigned KYLIN-3587:
--
Assignee: Yichen Zhou
> Null value is used in IllegalStateException message
> ---
>
> Key: KYLIN-3587
> URL: https://issues.apache.org/jira/browse/KYLIN-3587
> Project: Kylin
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yichen Zhou
>Priority: Minor
>
> In ProjectManager :
> {code}
> TableDesc table = metaMgr.getTableDesc(tableId, projectName);
> if (table == null) {
> throw new IllegalStateException("Cannot find table '" +
> table + "' in metadata manager");
> {code}
> Since table is null, the exception message is not helpful.
> It seems including tableId in the message is better.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3562) TS conflict when kylin update metadata in HBase
[
https://issues.apache.org/jira/browse/KYLIN-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620010#comment-16620010
]
Yichen Zhou commented on KYLIN-3562:
Hi [~chitin], KYLIN-3531 was merged to master to fix this bug. If you use kylin
2.4, you can run this command and start Kylin again.
{quote}$KYLIN_HOME/bin/metastore.sh remove /user
{quote}
I hope this will help you!
> TS conflict when kylin update metadata in HBase
> ---
>
> Key: KYLIN-3562
> URL: https://issues.apache.org/jira/browse/KYLIN-3562
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v2.4.0
>Reporter: Lingang Deng
>Priority: Major
> Attachments: image-2018-09-17-16-40-56-212.png
>
>
> Error log was as follows,
> {code:java}
> org.apache.kylin.common.persistence.WriteConflictException: Overwriting
> conflict /user/admin, expect old TS 1536928877043, but it is 1536928907207
> at
> org.apache.kylin.storage.hbase.HBaseResourceStore.checkAndPutResourceImpl(HBaseResourceStore.java:325)
> at
> org.apache.kylin.common.persistence.ResourceStore.checkAndPutResourceCheckpoint(ResourceStore.java:318)
> at
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:303)
> at
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:282)
> at
> org.apache.kylin.metadata.cachesync.CachedCrudAssist.save(CachedCrudAssist.java:192){code}
>
> what disturbs me the most was that the error was happened several hours,
> then my all build job and query job failed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (KYLIN-3562) TS conflict when kylin update metadata in HBase
[
https://issues.apache.org/jira/browse/KYLIN-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617049#comment-16617049
]
Yichen Zhou edited comment on KYLIN-3562 at 9/17/18 3:43 AM:
-
[~chitin], I am working on KYLIN-3531 and maybe they have the same root cause.
I‘ll let you know if there is any progress.
was (Author: yichen.zhou):
[~chitin], I am working on KYLIN-3531 and maybe they have the same root cause.
Please refer to this: https://issues.apache.org/jira/browse/KYLIN-3531
I‘ll let you know if there is any progress.
> TS conflict when kylin update metadata in HBase
> ---
>
> Key: KYLIN-3562
> URL: https://issues.apache.org/jira/browse/KYLIN-3562
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v2.4.0
>Reporter: Lingang Deng
>Priority: Major
>
> Error log was as follows,
> {code:java}
> org.apache.kylin.common.persistence.WriteConflictException: Overwriting
> conflict /user/admin, expect old TS 1536928877043, but it is 1536928907207
> at
> org.apache.kylin.storage.hbase.HBaseResourceStore.checkAndPutResourceImpl(HBaseResourceStore.java:325)
> at
> org.apache.kylin.common.persistence.ResourceStore.checkAndPutResourceCheckpoint(ResourceStore.java:318)
> at
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:303)
> at
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:282)
> at
> org.apache.kylin.metadata.cachesync.CachedCrudAssist.save(CachedCrudAssist.java:192){code}
>
> what disturbs me the most was that the error was happened several hours,
> then my all build job and query job failed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3562) TS conflict when kylin update metadata in HBase
[
https://issues.apache.org/jira/browse/KYLIN-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617049#comment-16617049
]
Yichen Zhou commented on KYLIN-3562:
[~chitin], I am working on KYLIN-3531 and maybe they have the same root cause.
Please refer to this: https://issues.apache.org/jira/browse/KYLIN-3531
I‘ll let you know if there is any progress.
> TS conflict when kylin update metadata in HBase
> ---
>
> Key: KYLIN-3562
> URL: https://issues.apache.org/jira/browse/KYLIN-3562
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v2.4.0
>Reporter: Lingang Deng
>Priority: Major
>
> Error log was as follows,
> {code:java}
> org.apache.kylin.common.persistence.WriteConflictException: Overwriting
> conflict /user/admin, expect old TS 1536928877043, but it is 1536928907207
> at
> org.apache.kylin.storage.hbase.HBaseResourceStore.checkAndPutResourceImpl(HBaseResourceStore.java:325)
> at
> org.apache.kylin.common.persistence.ResourceStore.checkAndPutResourceCheckpoint(ResourceStore.java:318)
> at
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:303)
> at
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:282)
> at
> org.apache.kylin.metadata.cachesync.CachedCrudAssist.save(CachedCrudAssist.java:192){code}
>
> what disturbs me the most was that the error was happened several hours,
> then my all build job and query job failed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (KYLIN-3562) TS conflict when kylin update metadata in HBase
[
https://issues.apache.org/jira/browse/KYLIN-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617023#comment-16617023
]
Yichen Zhou edited comment on KYLIN-3562 at 9/17/18 3:11 AM:
-
Hi [~chitin], could you tell me when this error happened and in which step your
build job failed.
was (Author: yichen.zhou):
Hi [~chitin], could you tell me when this error happened and in which step your
build job fail.
> TS conflict when kylin update metadata in HBase
> ---
>
> Key: KYLIN-3562
> URL: https://issues.apache.org/jira/browse/KYLIN-3562
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v2.4.0
>Reporter: Lingang Deng
>Priority: Major
>
> Error log was as follows,
> {code:java}
> org.apache.kylin.common.persistence.WriteConflictException: Overwriting
> conflict /user/admin, expect old TS 1536928877043, but it is 1536928907207
> at
> org.apache.kylin.storage.hbase.HBaseResourceStore.checkAndPutResourceImpl(HBaseResourceStore.java:325)
> at
> org.apache.kylin.common.persistence.ResourceStore.checkAndPutResourceCheckpoint(ResourceStore.java:318)
> at
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:303)
> at
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:282)
> at
> org.apache.kylin.metadata.cachesync.CachedCrudAssist.save(CachedCrudAssist.java:192){code}
>
> what disturbs me the most was that the error was happened several hours,
> then my all build job and query job failed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3562) TS conflict when kylin update metadata in HBase
[
https://issues.apache.org/jira/browse/KYLIN-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617023#comment-16617023
]
Yichen Zhou commented on KYLIN-3562:
Hi [~chitin], could you tell me when this error happened and in which step your
build job fail.
> TS conflict when kylin update metadata in HBase
> ---
>
> Key: KYLIN-3562
> URL: https://issues.apache.org/jira/browse/KYLIN-3562
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v2.4.0
>Reporter: Lingang Deng
>Priority: Major
>
> Error log was as follows,
> {code:java}
> org.apache.kylin.common.persistence.WriteConflictException: Overwriting
> conflict /user/admin, expect old TS 1536928877043, but it is 1536928907207
> at
> org.apache.kylin.storage.hbase.HBaseResourceStore.checkAndPutResourceImpl(HBaseResourceStore.java:325)
> at
> org.apache.kylin.common.persistence.ResourceStore.checkAndPutResourceCheckpoint(ResourceStore.java:318)
> at
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:303)
> at
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:282)
> at
> org.apache.kylin.metadata.cachesync.CachedCrudAssist.save(CachedCrudAssist.java:192){code}
>
> what disturbs me the most was that the error was happened several hours,
> then my all build job and query job failed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (KYLIN-3543) Unclosed Job instance in CreateHTableJob#exportHBaseConfiguration
[
https://issues.apache.org/jira/browse/KYLIN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16606656#comment-16606656
]
Yichen Zhou edited comment on KYLIN-3543 at 9/10/18 7:45 AM:
-
Thank you Ted. The job configuration is saved in HDFS for later use. Please
refer to this: https://issues.apache.org/jira/browse/KYLIN-3446
Since we could not connect HBase in spark, this job should remain open until
spark use it in "convert to HFlie" step. However, when building cube with MR,
this job does become useless. But I think it's ok for the little cost.
was (Author: yichen.zhou):
Thank you Ted. The job configuration is saved in HDFS for later use. Please
refer to this: https://issues.apache.org/jira/browse/KYLIN-3446
Since we could not connect HBase in spark, this job should remain open until
spark use it in "convert to HFlie" step. However, when building cube with MR,
this job does become unless. But I think it's ok for the little cost.
> Unclosed Job instance in CreateHTableJob#exportHBaseConfiguration
> -
>
> Key: KYLIN-3543
> URL: https://issues.apache.org/jira/browse/KYLIN-3543
> Project: Kylin
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Minor
>
> {code}
> out = fs.create(new Path(hbaseConfPath));
> job.getConfiguration().writeXml(out);
> {code}
> The job instance should be closed upon return from the method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KYLIN-3547) DimensionRangeInfo: Unsupported data type boolean
Yichen Zhou created KYLIN-3547:
--
Summary: DimensionRangeInfo: Unsupported data type boolean
Key: KYLIN-3547
URL: https://issues.apache.org/jira/browse/KYLIN-3547
Project: Kylin
Issue Type: Bug
Components: Job Engine
Reporter: Yichen Zhou
In Extract Fact Table Distinct Columns Step, Kylin can not get dimension range
information from data of boolean type because DataType.getOrder() does not
support boolean.
{quote}java.lang.RuntimeException: error execute
org.apache.kylin.engine.spark.SparkFactDistinct at
org.apache.kylin.common.util.AbstractApplication.execute(AbstractApplication.java:42)
at org.apache.kylin.common.util.SparkEntry.main(SparkEntry.java:44) at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498) at
org.apache.spark.deploy.yarn.ApplicationMaster$$anon$2.run(ApplicationMaster.scala:636)
Caused by: org.apache.spark.SparkException: Job aborted due to stage failure:
Task 5 in stage 1.0 failed 4 times, most recent failure: Lost task 5.3 in stage
1.0 (TID 17, slave1.kcluster, executor 5): java.lang.IllegalArgumentException:
Unsupported data type boolean at
org.apache.kylin.metadata.datatype.DataTypeOrder.getInstance(DataTypeOrder.java:53)
at org.apache.kylin.metadata.datatype.DataType.getOrder(DataType.java:230) at
org.apache.kylin.metadata.datatype.DataType.compare(DataType.java:236) at
org.apache.kylin.engine.spark.SparkFactDistinct$MultiOutputFunction.call(SparkFactDistinct.java:739)
at
org.apache.kylin.engine.spark.SparkFactDistinct$MultiOutputFunction.call(SparkFactDistinct.java:612)
at
org.apache.spark.api.java.JavaRDDLike$$anonfun$fn$7$1.apply(JavaRDDLike.scala:186)
at
org.apache.spark.api.java.JavaRDDLike$$anonfun$fn$7$1.apply(JavaRDDLike.scala:186)
at
org.apache.spark.rdd.RDD$$anonfun$mapPartitions$1$$anonfun$apply$23.apply(RDD.scala:797)
at
org.apache.spark.rdd.RDD$$anonfun$mapPartitions$1$$anonfun$apply$23.apply(RDD.scala:797)
at org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:38) at
org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:323) at
org.apache.spark.rdd.RDD.iterator(RDD.scala:287) at
org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:87) at
org.apache.spark.scheduler.Task.run(Task.scala:99) at
org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:325) at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3543) Unclosed Job instance in CreateHTableJob#exportHBaseConfiguration
[
https://issues.apache.org/jira/browse/KYLIN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16606656#comment-16606656
]
Yichen Zhou commented on KYLIN-3543:
Thank you Ted. The job configuration is saved in HDFS for later use. Please
refer to this: https://issues.apache.org/jira/browse/KYLIN-3446
Since we could not connect HBase in spark, this job should remain open until
spark use it in "convert to HFlie" step. However, when building cube with MR,
this job does become unless. But I think it's ok for the little cost.
> Unclosed Job instance in CreateHTableJob#exportHBaseConfiguration
> -
>
> Key: KYLIN-3543
> URL: https://issues.apache.org/jira/browse/KYLIN-3543
> Project: Kylin
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Minor
>
> {code}
> out = fs.create(new Path(hbaseConfPath));
> job.getConfiguration().writeXml(out);
> {code}
> The job instance should be closed upon return from the method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KYLIN-3541) TableACLManagerTest failed
[
https://issues.apache.org/jira/browse/KYLIN-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yichen Zhou updated KYLIN-3541:
---
Description:
2018-09-05 11:11:27,013 ERROR [pool-179-thread-1] cachesync.Broadcaster:137 :
Announce broadcast event failed, targetNode localhost:49607 broadcastEvent
BroadcastEvent\{entity=table_acl, event=create, cacheKey=default}, error msg:
org.apache.http.conn.HttpHostConnectException: Connection to
[http://localhost:49607|http://localhost:49607/]
refused 2018-09-05 11:11:27,013 ERROR [pool-179-thread-1]
cachesync.Broadcaster:330 : Announce broadcast event exceeds retry limit,
abandon targetNode localhost:49607 broadcastEvent
BroadcastEvent\{entity=table_acl, event=create, cacheKey=default} 2018-09-05
11:11:27,015 INFO [main] server.AbstractConnector:318 : Stopped
ServerConnector@664c7565{HTTP/1.1,[http/1.1]}
{0.0.0.0:49607}
2018-09-05 11:11:27,015 INFO [main] handler.ContextHandler:910 : Stopped
o.e.j.s.ServletContextHandler@515a8659\{/,null,UNAVAILABLE} 2018-09-05
11:11:27,026 INFO [main] common.KylinConfig:113 : Destroy KylinConfig [ERROR]
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.932 s <<<
FAILURE! - in org.apache.kylin.rest.security.TableACLManagerTest [ERROR]
test(org.apache.kylin.rest.security.TableACLManagerTest) Time elapsed: 2.856 s
<<< FAILURE! java.lang.AssertionError: expected:<1> but was:<0> at
org.apache.kylin.rest.security.TableACLManagerTest.test(TableACLManagerTest.java:50)
mvn test in sandbox:
2018-09-05 12:09:20,203 DEBUG [Thread-3] util.ZookeeperDistributedLock:223 :
31...@sandbox.hortonworks.com trying to unlock
/kylin/../examples/test_metadata/job_engine/global_job_engine_lock
Exception in thread "Thread-3" java.lang.RuntimeException: Error while peeking
at /kylin/../examples/test_metadata/job_engine/global_job_engine_lock
at
org.apache.kylin.storage.hbase.util.ZookeeperDistributedLock.peekLock(ZookeeperDistributedLock.java:205)
at
org.apache.kylin.storage.hbase.util.ZookeeperDistributedLock.unlock(ZookeeperDistributedLock.java:225)
at
org.apache.kylin.storage.hbase.util.ZookeeperDistributedLock.unlockJobEngine(ZookeeperDistributedLock.java:312)
at
org.apache.kylin.storage.hbase.util.ZookeeperJobLock.unlockJobEngine(ZookeeperJobLock.java:86)
at
org.apache.kylin.job.impl.threadpool.DefaultScheduler.shutdown(DefaultScheduler.java:194)
at org.apache.kylin.rest.service.JobService$2.run(JobService.java:143)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: instance must be started before
calling this method
at
org.apache.curator.shaded.com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.getData(CuratorFrameworkImpl.java:375)
at
org.apache.kylin.storage.hbase.util.ZookeeperDistributedLock.peekLock(ZookeeperDistributedLock.java:200)
... 6 more
was:
2018-09-05 11:11:27,013 ERROR [pool-179-thread-1] cachesync.Broadcaster:137 :
Announce broadcast event failed, targetNode localhost:49607 broadcastEvent
BroadcastEvent\{entity=table_acl, event=create, cacheKey=default}, error msg:
org.apache.http.conn.HttpHostConnectException: Connection to
[http://localhost:49607|http://localhost:49607/]
refused 2018-09-05 11:11:27,013 ERROR [pool-179-thread-1]
cachesync.Broadcaster:330 : Announce broadcast event exceeds retry limit,
abandon targetNode localhost:49607 broadcastEvent
BroadcastEvent\{entity=table_acl, event=create, cacheKey=default} 2018-09-05
11:11:27,015 INFO [main] server.AbstractConnector:318 : Stopped
ServerConnector@664c7565\{HTTP/1.1,[http/1.1]}{0.0.0.0:49607} 2018-09-05
11:11:27,015 INFO [main] handler.ContextHandler:910 : Stopped
o.e.j.s.ServletContextHandler@515a8659\{/,null,UNAVAILABLE} 2018-09-05
11:11:27,026 INFO [main] common.KylinConfig:113 : Destroy KylinConfig [ERROR]
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.932 s <<<
FAILURE! - in org.apache.kylin.rest.security.TableACLManagerTest [ERROR]
test(org.apache.kylin.rest.security.TableACLManagerTest) Time elapsed: 2.856 s
<<< FAILURE! java.lang.AssertionError: expected:<1> but was:<0> at
org.apache.kylin.rest.security.TableACLManagerTest.test(TableACLManagerTest.java:50)
> TableACLManagerTest failed
> --
>
> Key: KYLIN-3541
> URL: https://issues.apache.org/jira/browse/KYLIN-3541
> Project: Kylin
> Issue Type: Bug
>Reporter: Yichen Zhou
>Priority: Major
>
> 2018-09-05 11:11:27,013 ERROR [pool-179-thread-1] cachesync.Broadcaster:137 :
> Announce broadcast event failed, targetNode localhost:49607 broadcastEvent
> BroadcastEvent\{entity=table_acl, event=create, cacheKey=default}, error msg:
> org.apache.http.conn.HttpHostConnectException: Connection to
> [http://localhost:49607|http://localhost:49607/]
> refused
[jira] [Created] (KYLIN-3541) TableACLManagerTest failed
Yichen Zhou created KYLIN-3541:
--
Summary: TableACLManagerTest failed
Key: KYLIN-3541
URL: https://issues.apache.org/jira/browse/KYLIN-3541
Project: Kylin
Issue Type: Bug
Reporter: Yichen Zhou
2018-09-05 11:11:27,013 ERROR [pool-179-thread-1] cachesync.Broadcaster:137 :
Announce broadcast event failed, targetNode localhost:49607 broadcastEvent
BroadcastEvent\{entity=table_acl, event=create, cacheKey=default}, error msg:
org.apache.http.conn.HttpHostConnectException: Connection to
[http://localhost:49607|http://localhost:49607/]
refused 2018-09-05 11:11:27,013 ERROR [pool-179-thread-1]
cachesync.Broadcaster:330 : Announce broadcast event exceeds retry limit,
abandon targetNode localhost:49607 broadcastEvent
BroadcastEvent\{entity=table_acl, event=create, cacheKey=default} 2018-09-05
11:11:27,015 INFO [main] server.AbstractConnector:318 : Stopped
ServerConnector@664c7565\{HTTP/1.1,[http/1.1]}{0.0.0.0:49607} 2018-09-05
11:11:27,015 INFO [main] handler.ContextHandler:910 : Stopped
o.e.j.s.ServletContextHandler@515a8659\{/,null,UNAVAILABLE} 2018-09-05
11:11:27,026 INFO [main] common.KylinConfig:113 : Destroy KylinConfig [ERROR]
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.932 s <<<
FAILURE! - in org.apache.kylin.rest.security.TableACLManagerTest [ERROR]
test(org.apache.kylin.rest.security.TableACLManagerTest) Time elapsed: 2.856 s
<<< FAILURE! java.lang.AssertionError: expected:<1> but was:<0> at
org.apache.kylin.rest.security.TableACLManagerTest.test(TableACLManagerTest.java:50)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (KYLIN-3521) Enable Cube Planner by default
[
https://issues.apache.org/jira/browse/KYLIN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603863#comment-16603863
]
Yichen Zhou edited comment on KYLIN-3521 at 9/5/18 3:38 AM:
It seems like KYLIN_3521_V2.patch forgot to set
"kylin.cube.cubeplanner.enabled" to true in
_kylin\server\src\test\java\org\apache\kylin\rest\service\AdminServiceTest.java_,
which may cause build failure.
{quote}2018-09-04 21:06:45,310 INFO [main] common.KylinConfig:113 : Destroy
KylinConfig[ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time
elapsed: 0.136 s <<< FAILURE! - in
org.apache.kylin.rest.service.AdminServiceTest[ERROR]
testGetPublicConfig(org.apache.kylin.rest.service.AdminServiceTest) Time
elapsed: 0.063 s <<< FAILURE!org.junit.ComparisonFailure:
expected:<...cubeplanner.enabled=[fals]e
kylin.web.help=
ky...> but was:<...cubeplanner.enabled=[tru]e
kylin.web.help=
ky...>
at
org.apache.kylin.rest.service.AdminServiceTest.testGetPublicConfig(AdminServiceTest.java:77)
{quote}
was (Author: yichen.zhou):
It seems like KYLIN_3521_V2.patch forgot to set
"kylin.cube.cubeplanner.enabled" to true in
_kylin\server\src\test\java\org\apache\kylin\rest\service\AdminServiceTest.java_,
which may cause build failure.
2018-09-04 21:06:45,310 INFO [main] common.KylinConfig:113 : Destroy
KylinConfig[ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time
elapsed: 0.136 s <<< FAILURE! - in
org.apache.kylin.rest.service.AdminServiceTest[ERROR]
testGetPublicConfig(org.apache.kylin.rest.service.AdminServiceTest) Time
elapsed: 0.063 s <<< FAILURE!org.junit.ComparisonFailure:
expected:<...cubeplanner.enabled=[fals]e
kylin.web.help=
ky...> but was:<...cubeplanner.enabled=[tru]e
kylin.web.help=
ky...>
at
org.apache.kylin.rest.service.AdminServiceTest.testGetPublicConfig(AdminServiceTest.java:77)
> Enable Cube Planner by default
> --
>
> Key: KYLIN-3521
> URL: https://issues.apache.org/jira/browse/KYLIN-3521
> Project: Kylin
> Issue Type: Improvement
>Affects Versions: v2.5.0
>Reporter: Shaofeng SHI
>Assignee: Ma Gang
>Priority: Minor
> Fix For: v2.5.0
>
> Attachments: KYLIN-3521_V2.patch
>
>
> Cube planner can significantly reduce the cuboid number that to build. As it
> wasn't enabled by default in 2.3 and 2.4, many users don't know that.
>
> To let more user to start using it, I suggest to enable it by default.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (KYLIN-3521) Enable Cube Planner by default
[ https://issues.apache.org/jira/browse/KYLIN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603863#comment-16603863 ] Yichen Zhou edited comment on KYLIN-3521 at 9/5/18 3:33 AM: It seems like KYLIN_3521_V2.patch forgot to set "kylin.cube.cubeplanner.enabled" to true in _kylin\server\src\test\java\org\apache\kylin\rest\service\AdminServiceTest.java_, which may cause build failure. 2018-09-04 21:06:45,310 INFO [main] common.KylinConfig:113 : Destroy KylinConfig[ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.136 s <<< FAILURE! - in org.apache.kylin.rest.service.AdminServiceTest[ERROR] testGetPublicConfig(org.apache.kylin.rest.service.AdminServiceTest) Time elapsed: 0.063 s <<< FAILURE!org.junit.ComparisonFailure: expected:<...cubeplanner.enabled=[fals]e kylin.web.help= ky...> but was:<...cubeplanner.enabled=[tru]e kylin.web.help= ky...> at org.apache.kylin.rest.service.AdminServiceTest.testGetPublicConfig(AdminServiceTest.java:77) was (Author: yichen.zhou): It seems like KYLIN_3521_V2.patch __ forgot to set "kylin.cube.cubeplanner.enabled" to true in _kylin\server\src\test\java\org\apache\kylin\rest\service\AdminServiceTest.java_, which may cause build failure. [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.136 s <<< FAILURE! - in org.apache.kylin.rest.service.AdminServiceTest[ERROR] testGetPublicConfig(org.apache.kylin.rest.service.AdminServiceTest) Time elapsed: 0.063 s <<< FAILURE!org.junit.ComparisonFailure: expected:<...cubeplanner.enabled=[fals]e kylin.web.help= ky...> but was:<...cubeplanner.enabled=[tru]e kylin.web.help= ky...> at org.apache.kylin.rest.service.AdminServiceTest.testGetPublicConfig(AdminServiceTest.java:77) > Enable Cube Planner by default > -- > > Key: KYLIN-3521 > URL: https://issues.apache.org/jira/browse/KYLIN-3521 > Project: Kylin > Issue Type: Improvement >Affects Versions: v2.5.0 >Reporter: Shaofeng SHI >Assignee: Ma Gang >Priority: Minor > Fix For: v2.5.0 > > Attachments: KYLIN-3521_V2.patch > > > Cube planner can significantly reduce the cuboid number that to build. As it > wasn't enabled by default in 2.3 and 2.4, many users don't know that. > > To let more user to start using it, I suggest to enable it by default. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (KYLIN-3521) Enable Cube Planner by default
[ https://issues.apache.org/jira/browse/KYLIN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603863#comment-16603863 ] Yichen Zhou edited comment on KYLIN-3521 at 9/5/18 3:31 AM: It seems like KYLIN_3521_V2.patch __ forgot to set "kylin.cube.cubeplanner.enabled" to true in _kylin\server\src\test\java\org\apache\kylin\rest\service\AdminServiceTest.java_, which may cause build failure. [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.136 s <<< FAILURE! - in org.apache.kylin.rest.service.AdminServiceTest[ERROR] testGetPublicConfig(org.apache.kylin.rest.service.AdminServiceTest) Time elapsed: 0.063 s <<< FAILURE!org.junit.ComparisonFailure: expected:<...cubeplanner.enabled=[fals]e kylin.web.help= ky...> but was:<...cubeplanner.enabled=[tru]e kylin.web.help= ky...> at org.apache.kylin.rest.service.AdminServiceTest.testGetPublicConfig(AdminServiceTest.java:77) was (Author: yichen.zhou): It seems like KYLIN-3521_V2.patch forgot to set "kylin.cube.cubeplanner.enabled" to true in _kylin\server\src\test\java\org\apache\kylin\rest\service\AdminServiceTest.java_, which may cause build failure. [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.136 s <<< FAILURE! - in org.apache.kylin.rest.service.AdminServiceTest[ERROR] testGetPublicConfig(org.apache.kylin.rest.service.AdminServiceTest) Time elapsed: 0.063 s <<< FAILURE!org.junit.ComparisonFailure: expected:<...cubeplanner.enabled=[fals]e kylin.web.help= ky...> but was:<...cubeplanner.enabled=[tru]e kylin.web.help= ky...> at org.apache.kylin.rest.service.AdminServiceTest.testGetPublicConfig(AdminServiceTest.java:77) > Enable Cube Planner by default > -- > > Key: KYLIN-3521 > URL: https://issues.apache.org/jira/browse/KYLIN-3521 > Project: Kylin > Issue Type: Improvement >Affects Versions: v2.5.0 >Reporter: Shaofeng SHI >Assignee: Ma Gang >Priority: Minor > Fix For: v2.5.0 > > Attachments: KYLIN-3521_V2.patch > > > Cube planner can significantly reduce the cuboid number that to build. As it > wasn't enabled by default in 2.3 and 2.4, many users don't know that. > > To let more user to start using it, I suggest to enable it by default. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3521) Enable Cube Planner by default
[ https://issues.apache.org/jira/browse/KYLIN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603863#comment-16603863 ] Yichen Zhou commented on KYLIN-3521: It seems like KYLIN-3521_V2.patch forgot to set "kylin.cube.cubeplanner.enabled" to true in _kylin\server\src\test\java\org\apache\kylin\rest\service\AdminServiceTest.java_, which may cause build failure. [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.136 s <<< FAILURE! - in org.apache.kylin.rest.service.AdminServiceTest[ERROR] testGetPublicConfig(org.apache.kylin.rest.service.AdminServiceTest) Time elapsed: 0.063 s <<< FAILURE!org.junit.ComparisonFailure: expected:<...cubeplanner.enabled=[fals]e kylin.web.help= ky...> but was:<...cubeplanner.enabled=[tru]e kylin.web.help= ky...> at org.apache.kylin.rest.service.AdminServiceTest.testGetPublicConfig(AdminServiceTest.java:77) > Enable Cube Planner by default > -- > > Key: KYLIN-3521 > URL: https://issues.apache.org/jira/browse/KYLIN-3521 > Project: Kylin > Issue Type: Improvement >Affects Versions: v2.5.0 >Reporter: Shaofeng SHI >Assignee: Ma Gang >Priority: Minor > Fix For: v2.5.0 > > Attachments: KYLIN-3521_V2.patch > > > Cube planner can significantly reduce the cuboid number that to build. As it > wasn't enabled by default in 2.3 and 2.4, many users don't know that. > > To let more user to start using it, I suggest to enable it by default. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KYLIN-3535) kylin-port-replace-util.sh could not take effect
[
https://issues.apache.org/jira/browse/KYLIN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yichen Zhou reassigned KYLIN-3535:
--
Assignee: Yichen Zhou
> kylin-port-replace-util.sh could not take effect
> -
>
> Key: KYLIN-3535
> URL: https://issues.apache.org/jira/browse/KYLIN-3535
> Project: Kylin
> Issue Type: Bug
> Components: Others
>Reporter: Yichen Zhou
>Assignee: Yichen Zhou
>Priority: Major
>
> $KYLIN_HOME/bin/kylin-port-replace-util.sh replace web servers port in
> kylin.properties:
> {quote}sed -i
> "s/kylin.server.cluster-servers=\(.*\).*:\(.*\)/kylin.server.cluster-servers=\1:${new_kylin_port}/g"
> ${KYLIN_CONFIG_FILE}
> {quote}
> However, all configurations in kylin.properties are commented out by default.
> New port numbers will not take effect unless being uncommented manually.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KYLIN-3534) Failed at update cube info step
[
https://issues.apache.org/jira/browse/KYLIN-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yichen Zhou updated KYLIN-3534:
---
Description:
When building cube with spark(full build), I got the following error in the
step of "Update Cube Info":
{quote}2018-09-04 14:49:49,007 INFO [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699]
steps.UpdateCubeInfoAfterBuildStep:158 : updateSegment step. TRANS_ID
minValue:x�3�.�) maxValue:null
2018-09-04 14:49:49,008 ERROR [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.AbstractExecutable:165 :
error running Executable:
UpdateCubeInfoAfterBuildStep\{id=d05156bb-2635-cb2f-ac19-b38f6147fcb2-09,
name=Update Cube Info, state=RUNNING}
2018-09-04 14:49:49,011 INFO [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.ExecutableManager:434 : job
id:d05156bb-2635-cb2f-ac19-b38f6147fcb2-09 from RUNNING to ERROR
2018-09-04 14:49:49,012 ERROR [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.AbstractExecutable:165 :
error running Executable: CubingJob\{id=d05156bb-2635-cb2f-ac19-b38f6147fcb2,
name=BUILD CUBE - cube_global_dictionary_spark - FULL_BUILD - GMT+08:00
2018-09-04 11:51:58, state=RUNNING}
2018-09-04 14:49:49,014 DEBUG [pool-6-thread-1] cachesync.Broadcaster:113 :
Servers in the cluster: [localhost:7070]
2018-09-04 14:49:49,014 DEBUG [pool-6-thread-1] cachesync.Broadcaster:123 :
Announcing new broadcast to all: BroadcastEvent\{entity=execute_output,
event=update, cacheKey=d05156bb-2635-cb2f-ac19-b38f6147fcb2}
2018-09-04 14:49:49,015 INFO [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.ExecutableManager:434 : job
id:d05156bb-2635-cb2f-ac19-b38f6147fcb2 from RUNNING to ERROR
2018-09-04 14:49:49,015 DEBUG [pool-6-thread-1] cachesync.Broadcaster:113 :
Servers in the cluster: [localhost:7070]
2018-09-04 14:49:49,015 DEBUG [pool-6-thread-1] cachesync.Broadcaster:123 :
Announcing new broadcast to all: BroadcastEvent\{entity=execute_output,
event=update, cacheKey=d05156bb-2635-cb2f-ac19-b38f6147fcb2}
2018-09-04 14:49:49,015 DEBUG [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.AbstractExecutable:316 : no
need to send email, user list is empty
2018-09-04 14:49:49,017 ERROR [pool-10-thread-10]
threadpool.DefaultScheduler:115 : ExecuteException
job:d05156bb-2635-cb2f-ac19-b38f6147fcb2
org.apache.kylin.job.exception.ExecuteException:
org.apache.kylin.job.exception.ExecuteException:java.lang.IllegalStateException
at org.apache.kylin.cube.DimensionRangeInfo.(DimensionRangeInfo.java:86)
at
org.apache.kylin.engine.mr.steps.UpdateCubeInfoAfterBuildStep.updateSegment(UpdateCubeInfoAfterBuildStep.java:166)
at
org.apache.kylin.engine.mr.steps.UpdateCubeInfoAfterBuildStep.doWork(UpdateCubeInfoAfterBuildStep.java:85)
at
org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:163)
at
org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:69)
at
org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:163)
at
org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:113)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{quote}
was:
When building sample cube with spark(full build), I got the following error in
the step of "Update Cube Info":
{quote}2018-09-04 14:49:49,007 INFO [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699]
steps.UpdateCubeInfoAfterBuildStep:158 : updateSegment step. TRANS_ID
minValue:x�3�.�) maxValue:null
2018-09-04 14:49:49,008 ERROR [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.AbstractExecutable:165 :
error running Executable:
UpdateCubeInfoAfterBuildStep\{id=d05156bb-2635-cb2f-ac19-b38f6147fcb2-09,
name=Update Cube Info, state=RUNNING}
2018-09-04 14:49:49,011 INFO [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.ExecutableManager:434 : job
id:d05156bb-2635-cb2f-ac19-b38f6147fcb2-09 from RUNNING to ERROR
2018-09-04 14:49:49,012 ERROR [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.AbstractExecutable:165 :
error running Executable: CubingJob\{id=d05156bb-2635-cb2f-ac19-b38f6147fcb2,
name=BUILD CUBE - cube_global_dictionary_spark - FULL_BUILD - GMT+08:00
2018-09-04 11:51:58, state=RUNNING}
2018-09-04 14:49:49,014 DEBUG [pool-6-thread-1] cachesync.Broadcaster:113 :
Servers in the cluster: [localhost:7070]
2018-09-04 14:49:49,014 DEBUG [pool-6-thread-1] cachesync.Broadcaster:123 :
Announcing new broadcast to all: BroadcastEvent\{entity=execute_output,
event=update,
[jira] [Updated] (KYLIN-3534) Failed at update cube info step
[
https://issues.apache.org/jira/browse/KYLIN-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yichen Zhou updated KYLIN-3534:
---
Description:
When building sample cube with spark(full build), I got the following error in
the step of "Update Cube Info":
{quote}2018-09-04 14:49:49,007 INFO [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699]
steps.UpdateCubeInfoAfterBuildStep:158 : updateSegment step. TRANS_ID
minValue:x�3�.�) maxValue:null
2018-09-04 14:49:49,008 ERROR [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.AbstractExecutable:165 :
error running Executable:
UpdateCubeInfoAfterBuildStep\{id=d05156bb-2635-cb2f-ac19-b38f6147fcb2-09,
name=Update Cube Info, state=RUNNING}
2018-09-04 14:49:49,011 INFO [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.ExecutableManager:434 : job
id:d05156bb-2635-cb2f-ac19-b38f6147fcb2-09 from RUNNING to ERROR
2018-09-04 14:49:49,012 ERROR [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.AbstractExecutable:165 :
error running Executable: CubingJob\{id=d05156bb-2635-cb2f-ac19-b38f6147fcb2,
name=BUILD CUBE - cube_global_dictionary_spark - FULL_BUILD - GMT+08:00
2018-09-04 11:51:58, state=RUNNING}
2018-09-04 14:49:49,014 DEBUG [pool-6-thread-1] cachesync.Broadcaster:113 :
Servers in the cluster: [localhost:7070]
2018-09-04 14:49:49,014 DEBUG [pool-6-thread-1] cachesync.Broadcaster:123 :
Announcing new broadcast to all: BroadcastEvent\{entity=execute_output,
event=update, cacheKey=d05156bb-2635-cb2f-ac19-b38f6147fcb2}
2018-09-04 14:49:49,015 INFO [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.ExecutableManager:434 : job
id:d05156bb-2635-cb2f-ac19-b38f6147fcb2 from RUNNING to ERROR
2018-09-04 14:49:49,015 DEBUG [pool-6-thread-1] cachesync.Broadcaster:113 :
Servers in the cluster: [localhost:7070]
2018-09-04 14:49:49,015 DEBUG [pool-6-thread-1] cachesync.Broadcaster:123 :
Announcing new broadcast to all: BroadcastEvent\{entity=execute_output,
event=update, cacheKey=d05156bb-2635-cb2f-ac19-b38f6147fcb2}
2018-09-04 14:49:49,015 DEBUG [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.AbstractExecutable:316 : no
need to send email, user list is empty
2018-09-04 14:49:49,017 ERROR [pool-10-thread-10]
threadpool.DefaultScheduler:115 : ExecuteException
job:d05156bb-2635-cb2f-ac19-b38f6147fcb2
org.apache.kylin.job.exception.ExecuteException:
org.apache.kylin.job.exception.ExecuteException:java.lang.IllegalStateException
at org.apache.kylin.cube.DimensionRangeInfo.(DimensionRangeInfo.java:86)
at
org.apache.kylin.engine.mr.steps.UpdateCubeInfoAfterBuildStep.updateSegment(UpdateCubeInfoAfterBuildStep.java:166)
at
org.apache.kylin.engine.mr.steps.UpdateCubeInfoAfterBuildStep.doWork(UpdateCubeInfoAfterBuildStep.java:85)
at
org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:163)
at
org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:69)
at
org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:163)
at
org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:113)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{quote}
was:
When build sample cube with spark(full build), I got the following error in the
step of
{quote}2018-09-04 14:49:49,007 INFO [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699]
steps.UpdateCubeInfoAfterBuildStep:158 : updateSegment step. TRANS_ID
minValue:x�3�.�) maxValue:null
2018-09-04 14:49:49,008 ERROR [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.AbstractExecutable:165 :
error running Executable:
UpdateCubeInfoAfterBuildStep\{id=d05156bb-2635-cb2f-ac19-b38f6147fcb2-09,
name=Update Cube Info, state=RUNNING}
2018-09-04 14:49:49,011 INFO [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.ExecutableManager:434 : job
id:d05156bb-2635-cb2f-ac19-b38f6147fcb2-09 from RUNNING to ERROR
2018-09-04 14:49:49,012 ERROR [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.AbstractExecutable:165 :
error running Executable: CubingJob\{id=d05156bb-2635-cb2f-ac19-b38f6147fcb2,
name=BUILD CUBE - cube_global_dictionary_spark - FULL_BUILD - GMT+08:00
2018-09-04 11:51:58, state=RUNNING}
2018-09-04 14:49:49,014 DEBUG [pool-6-thread-1] cachesync.Broadcaster:113 :
Servers in the cluster: [localhost:7070]
2018-09-04 14:49:49,014 DEBUG [pool-6-thread-1] cachesync.Broadcaster:123 :
Announcing new broadcast to all: BroadcastEvent\{entity=execute_output,
event=update,
[jira] [Updated] (KYLIN-3534) Failed at update cube info step
[
https://issues.apache.org/jira/browse/KYLIN-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yichen Zhou updated KYLIN-3534:
---
Description:
When build sample cube with spark(full build), I got the following error in the
step of
{quote}2018-09-04 14:49:49,007 INFO [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699]
steps.UpdateCubeInfoAfterBuildStep:158 : updateSegment step. TRANS_ID
minValue:x�3�.�) maxValue:null
2018-09-04 14:49:49,008 ERROR [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.AbstractExecutable:165 :
error running Executable:
UpdateCubeInfoAfterBuildStep\{id=d05156bb-2635-cb2f-ac19-b38f6147fcb2-09,
name=Update Cube Info, state=RUNNING}
2018-09-04 14:49:49,011 INFO [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.ExecutableManager:434 : job
id:d05156bb-2635-cb2f-ac19-b38f6147fcb2-09 from RUNNING to ERROR
2018-09-04 14:49:49,012 ERROR [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.AbstractExecutable:165 :
error running Executable: CubingJob\{id=d05156bb-2635-cb2f-ac19-b38f6147fcb2,
name=BUILD CUBE - cube_global_dictionary_spark - FULL_BUILD - GMT+08:00
2018-09-04 11:51:58, state=RUNNING}
2018-09-04 14:49:49,014 DEBUG [pool-6-thread-1] cachesync.Broadcaster:113 :
Servers in the cluster: [localhost:7070]
2018-09-04 14:49:49,014 DEBUG [pool-6-thread-1] cachesync.Broadcaster:123 :
Announcing new broadcast to all: BroadcastEvent\{entity=execute_output,
event=update, cacheKey=d05156bb-2635-cb2f-ac19-b38f6147fcb2}
2018-09-04 14:49:49,015 INFO [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.ExecutableManager:434 : job
id:d05156bb-2635-cb2f-ac19-b38f6147fcb2 from RUNNING to ERROR
2018-09-04 14:49:49,015 DEBUG [pool-6-thread-1] cachesync.Broadcaster:113 :
Servers in the cluster: [localhost:7070]
2018-09-04 14:49:49,015 DEBUG [pool-6-thread-1] cachesync.Broadcaster:123 :
Announcing new broadcast to all: BroadcastEvent\{entity=execute_output,
event=update, cacheKey=d05156bb-2635-cb2f-ac19-b38f6147fcb2}
2018-09-04 14:49:49,015 DEBUG [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.AbstractExecutable:316 : no
need to send email, user list is empty
2018-09-04 14:49:49,017 ERROR [pool-10-thread-10]
threadpool.DefaultScheduler:115 : ExecuteException
job:d05156bb-2635-cb2f-ac19-b38f6147fcb2
org.apache.kylin.job.exception.ExecuteException:
org.apache.kylin.job.exception.ExecuteException:java.lang.IllegalStateException
at org.apache.kylin.cube.DimensionRangeInfo.(DimensionRangeInfo.java:86)
at
org.apache.kylin.engine.mr.steps.UpdateCubeInfoAfterBuildStep.updateSegment(UpdateCubeInfoAfterBuildStep.java:166)
at
org.apache.kylin.engine.mr.steps.UpdateCubeInfoAfterBuildStep.doWork(UpdateCubeInfoAfterBuildStep.java:85)
at
org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:163)
at
org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:69)
at
org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:163)
at
org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:113)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{quote}
was:
When build sample cube with spark(full build), I got the following error at
{quote}2018-09-04 14:49:49,007 INFO [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699]
steps.UpdateCubeInfoAfterBuildStep:158 : updateSegment step. TRANS_ID
minValue:x�3�.�) maxValue:null
2018-09-04 14:49:49,008 ERROR [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.AbstractExecutable:165 :
error running Executable:
UpdateCubeInfoAfterBuildStep\{id=d05156bb-2635-cb2f-ac19-b38f6147fcb2-09,
name=Update Cube Info, state=RUNNING}
2018-09-04 14:49:49,011 INFO [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.ExecutableManager:434 : job
id:d05156bb-2635-cb2f-ac19-b38f6147fcb2-09 from RUNNING to ERROR
2018-09-04 14:49:49,012 ERROR [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.AbstractExecutable:165 :
error running Executable: CubingJob\{id=d05156bb-2635-cb2f-ac19-b38f6147fcb2,
name=BUILD CUBE - cube_global_dictionary_spark - FULL_BUILD - GMT+08:00
2018-09-04 11:51:58, state=RUNNING}
2018-09-04 14:49:49,014 DEBUG [pool-6-thread-1] cachesync.Broadcaster:113 :
Servers in the cluster: [localhost:7070]
2018-09-04 14:49:49,014 DEBUG [pool-6-thread-1] cachesync.Broadcaster:123 :
Announcing new broadcast to all: BroadcastEvent\{entity=execute_output,
event=update, cacheKey=d05156bb-2635-cb2f-ac19-b38f6147fcb2}
2018-09-04 14:49:49,015 INFO
[jira] [Updated] (KYLIN-3534) Failed at update cube info step
[
https://issues.apache.org/jira/browse/KYLIN-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yichen Zhou updated KYLIN-3534:
---
Description:
When build sample cube with spark(full build), I got the following error at
{quote}2018-09-04 14:49:49,007 INFO [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699]
steps.UpdateCubeInfoAfterBuildStep:158 : updateSegment step. TRANS_ID
minValue:x�3�.�) maxValue:null
2018-09-04 14:49:49,008 ERROR [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.AbstractExecutable:165 :
error running Executable:
UpdateCubeInfoAfterBuildStep\{id=d05156bb-2635-cb2f-ac19-b38f6147fcb2-09,
name=Update Cube Info, state=RUNNING}
2018-09-04 14:49:49,011 INFO [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.ExecutableManager:434 : job
id:d05156bb-2635-cb2f-ac19-b38f6147fcb2-09 from RUNNING to ERROR
2018-09-04 14:49:49,012 ERROR [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.AbstractExecutable:165 :
error running Executable: CubingJob\{id=d05156bb-2635-cb2f-ac19-b38f6147fcb2,
name=BUILD CUBE - cube_global_dictionary_spark - FULL_BUILD - GMT+08:00
2018-09-04 11:51:58, state=RUNNING}
2018-09-04 14:49:49,014 DEBUG [pool-6-thread-1] cachesync.Broadcaster:113 :
Servers in the cluster: [localhost:7070]
2018-09-04 14:49:49,014 DEBUG [pool-6-thread-1] cachesync.Broadcaster:123 :
Announcing new broadcast to all: BroadcastEvent\{entity=execute_output,
event=update, cacheKey=d05156bb-2635-cb2f-ac19-b38f6147fcb2}
2018-09-04 14:49:49,015 INFO [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.ExecutableManager:434 : job
id:d05156bb-2635-cb2f-ac19-b38f6147fcb2 from RUNNING to ERROR
2018-09-04 14:49:49,015 DEBUG [pool-6-thread-1] cachesync.Broadcaster:113 :
Servers in the cluster: [localhost:7070]
2018-09-04 14:49:49,015 DEBUG [pool-6-thread-1] cachesync.Broadcaster:123 :
Announcing new broadcast to all: BroadcastEvent\{entity=execute_output,
event=update, cacheKey=d05156bb-2635-cb2f-ac19-b38f6147fcb2}
2018-09-04 14:49:49,015 DEBUG [Scheduler 158588 Job
d05156bb-2635-cb2f-ac19-b38f6147fcb2-699] execution.AbstractExecutable:316 : no
need to send email, user list is empty
2018-09-04 14:49:49,017 ERROR [pool-10-thread-10]
threadpool.DefaultScheduler:115 : ExecuteException
job:d05156bb-2635-cb2f-ac19-b38f6147fcb2
org.apache.kylin.job.exception.ExecuteException:
org.apache.kylin.job.exception.ExecuteException:java.lang.IllegalStateException
at org.apache.kylin.cube.DimensionRangeInfo.(DimensionRangeInfo.java:86)
at
org.apache.kylin.engine.mr.steps.UpdateCubeInfoAfterBuildStep.updateSegment(UpdateCubeInfoAfterBuildStep.java:166)
at
org.apache.kylin.engine.mr.steps.UpdateCubeInfoAfterBuildStep.doWork(UpdateCubeInfoAfterBuildStep.java:85)
at
org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:163)
at
org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:69)
at
org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:163)
at
org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:113)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{quote}
was:
java.lang.IllegalStateException
at
org.apache.kylin.cube.DimensionRangeInfo.(DimensionRangeInfo.java:86)
at
org.apache.kylin.engine.mr.steps.UpdateCubeInfoAfterBuildStep.updateSegment(UpdateCubeInfoAfterBuildStep.java:166)
at
org.apache.kylin.engine.mr.steps.UpdateCubeInfoAfterBuildStep.doWork(UpdateCubeInfoAfterBuildStep.java:85)
at
org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:163)
at
org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:69)
at
org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:163)
at
org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:113)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
> Failed at update cube info step
> ---
>
> Key: KYLIN-3534
> URL: https://issues.apache.org/jira/browse/KYLIN-3534
> Project: Kylin
> Issue Type: Bug
>Reporter: Yichen Zhou
>Priority: Major
>
> When build sample cube with spark(full build), I got the following error at
> {quote}2018-09-04 14:49:49,007 INFO [Scheduler 158588 Job
>
[jira] [Created] (KYLIN-3535) kylin-port-replace-util.sh could not take effect
Yichen Zhou created KYLIN-3535:
--
Summary: kylin-port-replace-util.sh could not take effect
Key: KYLIN-3535
URL: https://issues.apache.org/jira/browse/KYLIN-3535
Project: Kylin
Issue Type: Bug
Components: Others
Reporter: Yichen Zhou
$KYLIN_HOME/bin/kylin-port-replace-util.sh replace web servers port in
kylin.properties:
{quote}sed -i
"s/kylin.server.cluster-servers=\(.*\).*:\(.*\)/kylin.server.cluster-servers=\1:${new_kylin_port}/g"
${KYLIN_CONFIG_FILE}
{quote}
However, all configurations in kylin.properties are commented out by default.
New port numbers will not take effect unless being uncommented manually.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KYLIN-3534) Failed at update cube info step
Yichen Zhou created KYLIN-3534: -- Summary: Failed at update cube info step Key: KYLIN-3534 URL: https://issues.apache.org/jira/browse/KYLIN-3534 Project: Kylin Issue Type: Bug Reporter: Yichen Zhou java.lang.IllegalStateException at org.apache.kylin.cube.DimensionRangeInfo.(DimensionRangeInfo.java:86) at org.apache.kylin.engine.mr.steps.UpdateCubeInfoAfterBuildStep.updateSegment(UpdateCubeInfoAfterBuildStep.java:166) at org.apache.kylin.engine.mr.steps.UpdateCubeInfoAfterBuildStep.doWork(UpdateCubeInfoAfterBuildStep.java:85) at org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:163) at org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:69) at org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:163) at org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:113) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3531) Login failed with case-insensitive username
[
https://issues.apache.org/jira/browse/KYLIN-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yichen Zhou updated KYLIN-3531:
---
Fix Version/s: (was: v2.5.0)
> Login failed with case-insensitive username
> ---
>
> Key: KYLIN-3531
> URL: https://issues.apache.org/jira/browse/KYLIN-3531
> Project: Kylin
> Issue Type: Bug
> Components: Metadata
>Affects Versions: v2.4.0
>Reporter: Yichen Zhou
>Assignee: Yichen Zhou
>Priority: Major
>
> Username is case-insensitive in login authentication but case-sensitive in
> hbase metadata.
> {quote}org.apache.kylin.common.persistence.WriteConflictException:
> Overwriting conflict /user/Admin, expect old TS 1536031295060, but it is 0
>
> org.apache.kylin.storage.hbase.HBaseResourceStore.checkAndPutResourceImpl(HBaseResourceStore.java:325)
>
> org.apache.kylin.common.persistence.ResourceStore.checkAndPutResourceCheckpoint(ResourceStore.java:323)
>
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:308)
>
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:287)
>
> org.apache.kylin.metadata.cachesync.CachedCrudAssist.save(CachedCrudAssist.java:192)
>
> org.apache.kylin.rest.security.KylinUserManager.update(KylinUserManager.java:122)
>
> org.apache.kylin.rest.service.KylinUserService.updateUser(KylinUserService.java:85)
>
> org.apache.kylin.rest.security.KylinAuthenticationProvider.authenticate(KylinAuthenticationProvider.java:117)
>
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:174)
>
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:199)
>
> org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilterInternal(BasicAuthenticationFilter.java:180)
>
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KYLIN-3531) Login failed with case-insensitive username
Yichen Zhou created KYLIN-3531:
--
Summary: Login failed with case-insensitive username
Key: KYLIN-3531
URL: https://issues.apache.org/jira/browse/KYLIN-3531
Project: Kylin
Issue Type: Bug
Components: Metadata
Affects Versions: v2.4.0
Reporter: Yichen Zhou
Assignee: Yichen Zhou
Fix For: v2.5.0
Username is case-insensitive in login authentication but case-sensitive in
hbase metadata.
{quote}org.apache.kylin.common.persistence.WriteConflictException: Overwriting
conflict /user/Admin, expect old TS 1536031295060, but it is 0
org.apache.kylin.storage.hbase.HBaseResourceStore.checkAndPutResourceImpl(HBaseResourceStore.java:325)
org.apache.kylin.common.persistence.ResourceStore.checkAndPutResourceCheckpoint(ResourceStore.java:323)
org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:308)
org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:287)
org.apache.kylin.metadata.cachesync.CachedCrudAssist.save(CachedCrudAssist.java:192)
org.apache.kylin.rest.security.KylinUserManager.update(KylinUserManager.java:122)
org.apache.kylin.rest.service.KylinUserService.updateUser(KylinUserService.java:85)
org.apache.kylin.rest.security.KylinAuthenticationProvider.authenticate(KylinAuthenticationProvider.java:117)
org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:174)
org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:199)
org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilterInternal(BasicAuthenticationFilter.java:180)
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
{quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3521) Enable Cube Planner by default
[ https://issues.apache.org/jira/browse/KYLIN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598408#comment-16598408 ] Yichen Zhou commented on KYLIN-3521: +1 Good feature! And maybe we can make it easier to understand and use in phase two. > Enable Cube Planner by default > -- > > Key: KYLIN-3521 > URL: https://issues.apache.org/jira/browse/KYLIN-3521 > Project: Kylin > Issue Type: Improvement >Affects Versions: v2.5.0 >Reporter: Shaofeng SHI >Priority: Minor > > Cube planner can significantly reduce the cuboid number that to build. As it > wasn't enabled by default in 2.3 and 2.4, many users don't know that. > > To let more user to start using it, I suggest to enable it by default. As > Cube planner only works when build the first segment, it only affect the > cuboid scheduler of a new Cube. Old cubes will not be affected. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
