[jira] [Updated] (KYLIN-1820) Column autocomplete should remove the user input in model designer
[ https://issues.apache.org/jira/browse/KYLIN-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1820: - Attachment: 0001-KYLIN-1820-Column-autocomplete-should-remove-the-use.patch I have fixed this bug.Please check it. thanks! > Column autocomplete should remove the user input in model designer > -- > > Key: KYLIN-1820 > URL: https://issues.apache.org/jira/browse/KYLIN-1820 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.5.2 > Environment: OS:Mac > Safari/Chrome >Reporter: Billy(Yiming) Liu >Assignee: Zhong,Jason >Priority: Minor > Fix For: Backlog > > Attachments: > 0001-KYLIN-1820-Column-autocomplete-should-remove-the-use.patch > > > In step 3 add column dimension in Model Designer, user enters the column name > and the column name autocompletion pops up. When some item is selected, the > column name shows in the textbox. At this time, the selected column should > replace the user input, not insert before the user input. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2127) UI bug fix for Extend Column
[
https://issues.apache.org/jira/browse/KYLIN-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kangkaisen updated KYLIN-2127:
--
Attachment: KYLIN-2127.patch
This is the patch.
Please review the patch, thanks.
> UI bug fix for Extend Column
>
>
> Key: KYLIN-2127
> URL: https://issues.apache.org/jira/browse/KYLIN-2127
> Project: Kylin
> Issue Type: Bug
> Components: Web
>Affects Versions: v1.5.4.1
>Reporter: kangkaisen
>Assignee: kangkaisen
> Attachments: KYLIN-2127.patch
>
>
> In the 1.5.4.1 version of Kylin. we firstly add a new SUM(MAX, MIN...)
> measure and then add a Extend Column measure, finally save the cube will fail.
> Because of the json data of Extend Column measure is like this:
> {
> "name": "周起始日",
> "function": {
> "expression": "EXTENDED_COLUMN",
> "returntype": "extendedcolumn(100)",
> "parameter": {
> "type": "column",
> "value": "WK",
> "next_parameter": {
> "type": "column",
> "value": "WK_FROM",
> "next_parameter": {}
> }
> },
> "configuration": null
> }
> }
> the last {{next_parameter}} is {}, it should be null.
> This bug may be introduced by KYLIN-1767.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KYLIN-2127) UI bug fix for Extend Column
[
https://issues.apache.org/jira/browse/KYLIN-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kangkaisen updated KYLIN-2127:
--
Description:
In the 1.5.4.1 version of Kylin. we firstly add a new SUM(MAX, MIN...) measure
and then add a Extend Column measure, finally save the cube will fail.
Because of the json data of Extend Column measure is like this:
{
"name": "周起始日",
"function": {
"expression": "EXTENDED_COLUMN",
"returntype": "extendedcolumn(100)",
"parameter": {
"type": "column",
"value": "WK",
"next_parameter": {
"type": "column",
"value": "WK_FROM",
"next_parameter": {}
}
},
"configuration": null
}
}
the last {{next_parameter}} is {}, it should be null.
This bug may be introduced by KYLIN-1767.
was:
In the 1.5.4.1 version of Kylin. we firstly add a new SUM(MAX, MIN...) measure
and then add a Extend Column measure, finally save the cube will fail.
Because of the json data of Extend Column measure is like this:
{{{
"name": "周起始日",
"function": {
"expression": "EXTENDED_COLUMN",
"returntype": "extendedcolumn(100)",
"parameter": {
"type": "column",
"value": "WK",
"next_parameter": {
"type": "column",
"value": "WK_FROM",
"next_parameter": {}
}
},
"configuration": null
}
},}}.
the last {{next_parameter}} is {}, it should be null.
This bug may be introduced by KYLIN-1767.
> UI bug fix for Extend Column
>
>
> Key: KYLIN-2127
> URL: https://issues.apache.org/jira/browse/KYLIN-2127
> Project: Kylin
> Issue Type: Bug
> Components: Web
>Affects Versions: v1.5.4.1
>Reporter: kangkaisen
>Assignee: kangkaisen
>
> In the 1.5.4.1 version of Kylin. we firstly add a new SUM(MAX, MIN...)
> measure and then add a Extend Column measure, finally save the cube will fail.
> Because of the json data of Extend Column measure is like this:
> {
> "name": "周起始日",
> "function": {
> "expression": "EXTENDED_COLUMN",
> "returntype": "extendedcolumn(100)",
> "parameter": {
> "type": "column",
> "value": "WK",
> "next_parameter": {
> "type": "column",
> "value": "WK_FROM",
> "next_parameter": {}
> }
> },
> "configuration": null
> }
> }
> the last {{next_parameter}} is {}, it should be null.
> This bug may be introduced by KYLIN-1767.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KYLIN-2127) UI bug fix for Extend Column
[
https://issues.apache.org/jira/browse/KYLIN-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kangkaisen updated KYLIN-2127:
--
Description:
In the 1.5.4.1 version of Kylin. we firstly add a new SUM(MAX, MIN...) measure
and then add a Extend Column measure, finally save the cube will fail.
Because of the json data of Extend Column measure is like this:
{{{
"name": "周起始日",
"function": {
"expression": "EXTENDED_COLUMN",
"returntype": "extendedcolumn(100)",
"parameter": {
"type": "column",
"value": "WK",
"next_parameter": {
"type": "column",
"value": "WK_FROM",
"next_parameter": {}
}
},
"configuration": null
}
},}}.
the last {{next_parameter}} is {}, it should be null.
This bug may be introduced by KYLIN-1767.
was:
In the 1.5.4.1 version of Kylin. we firstly add a new SUM(MAX, MIN...) measure
and then add a Extend Column measure, finally save the cube will fail.
Because of the json data of Extend Column measure is like this:
{{{
"name": "周起始日",
"function": {
"expression": "EXTENDED_COLUMN",
"returntype": "extendedcolumn(100)",
"parameter": {
"type": "column",
"value": "WK",
"next_parameter": {
"type": "column",
"value": "WK_FROM",
"next_parameter": {}
}
},
"configuration": null
}
},}}.
the last {{next_parameter}} is {}, it should be null.
This bug may be introduced by KYLIN-1767.
> UI bug fix for Extend Column
>
>
> Key: KYLIN-2127
> URL: https://issues.apache.org/jira/browse/KYLIN-2127
> Project: Kylin
> Issue Type: Bug
> Components: Web
>Affects Versions: v1.5.4.1
>Reporter: kangkaisen
>Assignee: kangkaisen
>
> In the 1.5.4.1 version of Kylin. we firstly add a new SUM(MAX, MIN...)
> measure and then add a Extend Column measure, finally save the cube will fail.
> Because of the json data of Extend Column measure is like this:
> {{{
> "name": "周起始日",
> "function": {
> "expression": "EXTENDED_COLUMN",
> "returntype": "extendedcolumn(100)",
> "parameter": {
> "type": "column",
> "value": "WK",
> "next_parameter": {
> "type": "column",
> "value": "WK_FROM",
> "next_parameter": {}
> }
> },
> "configuration": null
> }
> },}}.
> the last {{next_parameter}} is {}, it should be null.
> This bug may be introduced by KYLIN-1767.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (KYLIN-990) backport KYLIN-697 to 0.7-staging branch(the new 1.0 branch)
[ https://issues.apache.org/jira/browse/KYLIN-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Li closed KYLIN-990. - Resolution: Won't Fix > backport KYLIN-697 to 0.7-staging branch(the new 1.0 branch) > > > Key: KYLIN-990 > URL: https://issues.apache.org/jira/browse/KYLIN-990 > Project: Kylin > Issue Type: Test > Components: Tools, Build and Test >Affects Versions: v1.1 >Reporter: hongbin ma >Assignee: Dong Li > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KYLIN-1993) Set default storage_type and engine_type in kylin.properties
[ https://issues.apache.org/jira/browse/KYLIN-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Li resolved KYLIN-1993. Resolution: Fixed Fix Version/s: v1.5.4.1 > Set default storage_type and engine_type in kylin.properties > > > Key: KYLIN-1993 > URL: https://issues.apache.org/jira/browse/KYLIN-1993 > Project: Kylin > Issue Type: Improvement >Reporter: Dong Li >Assignee: Dong Li > Fix For: v1.5.4.1 > > > To set default storage_type and engine_type in kylin.properties, which will > be used in sample.sh and frontend. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2127) UI bug fix for Extend Column
kangkaisen created KYLIN-2127:
-
Summary: UI bug fix for Extend Column
Key: KYLIN-2127
URL: https://issues.apache.org/jira/browse/KYLIN-2127
Project: Kylin
Issue Type: Bug
Components: Web
Affects Versions: v1.5.4.1
Reporter: kangkaisen
Assignee: kangkaisen
In the 1.5.4.1 version of Kylin. we firstly add a new SUM(MAX, MIN...) measure
and then add a Extend Column measure, finally save the cube will fail.
Because of the json data of Extend Column measure is like this:
{{{
"name": "周起始日",
"function": {
"expression": "EXTENDED_COLUMN",
"returntype": "extendedcolumn(100)",
"parameter": {
"type": "column",
"value": "WK",
"next_parameter": {
"type": "column",
"value": "WK_FROM",
"next_parameter": {}
}
},
"configuration": null
}
},}}.
the last {{next_parameter}} is {}, it should be null.
This bug may be introduced by KYLIN-1767.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KYLIN-1741) Enhance diagnosis tool
[ https://issues.apache.org/jira/browse/KYLIN-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Li resolved KYLIN-1741. Resolution: Fixed > Enhance diagnosis tool > -- > > Key: KYLIN-1741 > URL: https://issues.apache.org/jira/browse/KYLIN-1741 > Project: Kylin > Issue Type: Improvement > Components: Tools, Build and Test >Reporter: Dong Li >Assignee: Dong Li >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2024) kylin TopN only support the first measure
[ https://issues.apache.org/jira/browse/KYLIN-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Li updated KYLIN-2024: --- Assignee: Shaofeng SHI (was: Dong Li) > kylin TopN only support the first measure > -- > > Key: KYLIN-2024 > URL: https://issues.apache.org/jira/browse/KYLIN-2024 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v1.5.3 >Reporter: Kris >Assignee: Shaofeng SHI > Labels: newbie > Attachments: 截图 2016-09-18 15时18分54秒.jpg > > > when I build cube chose top-N and select the group by column ,like this > TOP_N SUM|ORDER BY:CLICK > GROUP BY:MEDIA_SLOT > TOP_N > SUM|ORDER BY:EREQ > GROUP BY:MEDIA_SLOT > TOP_N > SUM|ORDER BY:ECLICK > GROUP BY:MEDIA_DOMAIN > TOP_N > SUM|ORDER BY:REQUEST > GROUP BY:MEDIA_DOMAIN > if I use SQL likes "select MEDIA_SLOT ,sum(EREQ) ... ...group by (MEDIA_SLOT) > order by sum(EREQ) desc /asc limit 100" or group > by(MEDIA_DOMAIN),sum(REQUEST) the result gets none.But if sum(CLICK) group by > (MEDIA_SLOT) or sum(ECLICK) group by (MEDIA_DOMAIN) the result return true; > Best whishes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2116) when hive field delimitor exists in table field values, fields order is wrong
[ https://issues.apache.org/jira/browse/KYLIN-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15605405#comment-15605405 ] Dong Li commented on KYLIN-2116: I will fix this by adding a property 'kylin.job.hive.intermediatetable.delimitor' in KylinConfig, whose default value is \177. User could override the property in cube level. > when hive field delimitor exists in table field values, fields order is wrong > - > > Key: KYLIN-2116 > URL: https://issues.apache.org/jira/browse/KYLIN-2116 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v1.5.2 >Reporter: yubo >Assignee: Dong Li > > in #1 step when creating temp hive table,there is delimitor > > ROW FORMAT DELIMITED FIELDS TERMINATED BY '\177' > > when this delimitor exists in some fields, fields order is wrong > test details: > when we search with same sql, different results are returned as below. > 25 in kylin and 24 in hive. > We guess there maybe some problem within #2 Step(Extract Fact Table Distinct > Columns) when building cube. > 1 search in kylin > select distinct visit_hour from KYLIN_REPORT_DB.session_behavior_channel_oms > where visit_date >= '2016-10-19' and visit_date <= '2016-10-19' > Results (25) > 19 > 17 > 18 > 15 > 16 > 13 > 14 > 11 > 12 > 21 > 神马搜索 > 20 > 08 > 09 > 04 > 22 > 05 > 23 > 06 > 07 > 00 > 01 > 02 > 03 > 10 > 2. #2 Step Name: Extract Fact Table Distinct Columns output > hadoop fs -cat > /kylin/kylin_metadata/kylin-e8bb517d-6c29-4f89-a83e-871e142e3d48/channel_first_stage_flow_cube/fact_distinct_columns/VISIT_HOUR > > 00 > 01 > 02 > 03 > 04 > 05 > 06 > 07 > 08 > 09 > 10 > 11 > 12 > 13 > 14 > 15 > 16 > 17 > 18 > 19 > 20 > 21 > 22 > 23 > 神马搜索 > 3. hive table > hive -e " select distinct visit_hour from > KYLIN_REPORT_DB.session_behavior_channel_oms where visit_date >= > '2016-10-19' and visit_date <= '2016-10-19' " > WARNING: Use "yarn jar" to launch YARN applications. > Logging initialized using configuration in > file:/etc/hive/2.3.4.0-3485/0/hive-log4j.properties > Query ID = hdfs_20161020164441_dcea3e55-1a8b-4f3a-9378-7dcda008001b > Total jobs = 1 > Launching Job 1 out of 1 > Status: Running (Executing on YARN cluster with App id > application_1476342479107_13013) > > > VERTICES STATUS TOTAL COMPLETED RUNNING PENDING FAILED > KILLED > > > Map 1 .. SUCCEEDED56456400 0 > 0 > Reducer 2 .. SUCCEEDED 15 1500 0 > 0 > > > VERTICES: 02/02 [==>>] 100% ELAPSED TIME: 168.70 s > > > > OK > 03 > 12 > 13 > 22 > 05 > 14 > 08 > 17 > 00 > 02 > 18 > 06 > 23 > 01 > 19 > 07 > 10 > 15 > 20 > 16 > 11 > 04 > 09 > 21 > Time taken: 172.907 seconds, Fetched: 24 row(s) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KYLIN-2120) kylin1.5.4.1 with cdh5.7 cube sql Oops Faild to take action
[ https://issues.apache.org/jira/browse/KYLIN-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong,Jason reassigned KYLIN-2120: -- Assignee: Shaofeng SHI (was: Zhong,Jason) Shaofeng is working on this. > kylin1.5.4.1 with cdh5.7 cube sql Oops Faild to take action > --- > > Key: KYLIN-2120 > URL: https://issues.apache.org/jira/browse/KYLIN-2120 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: fanshengliang >Assignee: Shaofeng SHI > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2106) UI bug - Advanced Settings - Rowkeys - new Integer dictionary encoding - could possibly impact also cube metadata
[ https://issues.apache.org/jira/browse/KYLIN-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15605306#comment-15605306 ] Zhong,Jason commented on KYLIN-2106: this also happen when create encoding for top_n measure > UI bug - Advanced Settings - Rowkeys - new Integer dictionary encoding - > could possibly impact also cube metadata > - > > Key: KYLIN-2106 > URL: https://issues.apache.org/jira/browse/KYLIN-2106 > Project: Kylin > Issue Type: Bug > Components: Job Engine, Web >Affects Versions: v1.5.4.1 >Reporter: Richard Calaba >Assignee: Zhong,Jason > Fix For: v1.6.0 > > > I have realized possib,e bug in UI, to reproduce: > 1) Create Cube which has in Advance Settings - Rowkeys section a encoding of > one of the dimension (in my case it was 1st dimension - customer_id) set > encoding to 'Integer' - I used length 22. (Do not use the 'Int' Deprecated) > 2) Save this cube. > 3) Clone this cube > 4) The cloned cube had the same dimension in the Rowkeys section in Edit mode > marked as 'Int(deprecated)' and the length of the Int dictionary encoding was > set to 'ger' - obviously some issue while parsing the new Encoding type - > hopefully only on UI ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KYLIN-2126) use column name as default dimension name when auto generate dimension for lookup table
[
https://issues.apache.org/jira/browse/KYLIN-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhong,Jason resolved KYLIN-2126.
Resolution: Fixed
> use column name as default dimension name when auto generate dimension for
> lookup table
> ---
>
> Key: KYLIN-2126
> URL: https://issues.apache.org/jira/browse/KYLIN-2126
> Project: Kylin
> Issue Type: Improvement
> Components: Web
>Affects Versions: v1.5.4.1
>Reporter: Zhong,Jason
>Assignee: Zhong,Jason
> Fix For: v1.6.0
>
>
> now we use "{tableName}_derived" as dimension name, it better to use column
> name as default dimension name when auto generate dimension for lookup table
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KYLIN-2106) UI bug - Advanced Settings - Rowkeys - new Integer dictionary encoding - could possibly impact also cube metadata
[ https://issues.apache.org/jira/browse/KYLIN-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong,Jason resolved KYLIN-2106. Resolution: Fixed Fix Version/s: v1.6.0 > UI bug - Advanced Settings - Rowkeys - new Integer dictionary encoding - > could possibly impact also cube metadata > - > > Key: KYLIN-2106 > URL: https://issues.apache.org/jira/browse/KYLIN-2106 > Project: Kylin > Issue Type: Bug > Components: Job Engine, Web >Affects Versions: v1.5.4.1 >Reporter: Richard Calaba >Assignee: Zhong,Jason > Fix For: v1.6.0 > > > I have realized possib,e bug in UI, to reproduce: > 1) Create Cube which has in Advance Settings - Rowkeys section a encoding of > one of the dimension (in my case it was 1st dimension - customer_id) set > encoding to 'Integer' - I used length 22. (Do not use the 'Int' Deprecated) > 2) Save this cube. > 3) Clone this cube > 4) The cloned cube had the same dimension in the Rowkeys section in Edit mode > marked as 'Int(deprecated)' and the length of the Int dictionary encoding was > set to 'ger' - obviously some issue while parsing the new Encoding type - > hopefully only on UI ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1985) SnapshotTable should only keep the columns described in tableDesc
[ https://issues.apache.org/jira/browse/KYLIN-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15605256#comment-15605256 ] hongbin ma commented on KYLIN-1985: --- it got confirmed in https://issues.apache.org/jira/browse/KYLIN-2012?focusedCommentId=15571341=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15571341 > SnapshotTable should only keep the columns described in tableDesc > - > > Key: KYLIN-1985 > URL: https://issues.apache.org/jira/browse/KYLIN-1985 > Project: Kylin > Issue Type: Improvement > Components: Job Engine >Affects Versions: v1.5.3 >Reporter: zhengdong >Assignee: zhengdong > Fix For: v1.5.4 > > Attachments: KYLIN-1985.patch > > > we suffered from a strange problem that we got a > java.lang.ArrayIndexOutOfBoundsException when build of refresh a cube, > exception stack like this : > java.lang.IllegalStateException: Failed to load lookup table DIM_TABLE_NAME > from snapshot > /table_snapshot/dim_table_name/5a78a522-6f85-4650-b47d-6a5f5806b7f7.snapshot > at > org.apache.kylin.cube.CubeManager.getLookupTable(CubeManager.java:621) > at > org.apache.kylin.cube.cli.DictionaryGeneratorCLI.processSegment(DictionaryGeneratorCLI.java:61) > at > org.apache.kylin.cube.cli.DictionaryGeneratorCLI.processSegment(DictionaryGeneratorCLI.java:42) > at > org.apache.kylin.engine.mr.steps.CreateDictionaryJob.run(CreateDictionaryJob.java:56) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84) > at > org.apache.kylin.engine.mr.common.HadoopShellExecutable.doWork(HadoopShellExecutable.java:63) > at > org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:112) > at > org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:57) > at > org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:112) > at > org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:127) > 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: java.lang.ArrayIndexOutOfBoundsException: 19 > at > org.apache.kylin.dict.lookup.LookupStringTable.convertRow(LookupStringTable.java:85) > at > org.apache.kylin.dict.lookup.LookupStringTable.convertRow(LookupStringTable.java:34) > at org.apache.kylin.dict.lookup.LookupTable.initRow(LookupTable.java:76) > at org.apache.kylin.dict.lookup.LookupTable.init(LookupTable.java:67) > at > org.apache.kylin.dict.lookup.LookupStringTable.init(LookupStringTable.java:79) > at org.apache.kylin.dict.lookup.LookupTable.(LookupTable.java:55) > at > org.apache.kylin.dict.lookup.LookupStringTable.(LookupStringTable.java:65) > at > org.apache.kylin.cube.CubeManager.getLookupTable(CubeManager.java:619) > ... 13 more > and a simple exception when queried by a lookup table dimension > > ERROR [http-bio-7070-exec-7] controller.QueryController:209 : Exception when > execute sql > at org.apache.calcite.avatica.Helper.createException(Helper.java:56) > at org.apache.calcite.avatica.Helper.createException(Helper.java:41) > at > org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:143) > at > org.apache.calcite.avatica.AvaticaStatement.executeQuery(AvaticaStatement.java:186) > at > org.apache.kylin.rest.service.QueryService.execute(QueryService.java:366) > at > org.apache.kylin.rest.service.QueryService.queryWithSqlMassage(QueryService.java:278) > at > org.apache.kylin.rest.service.QueryService.query(QueryService.java:121) > at > org.apache.kylin.rest.service.QueryService$$FastClassByCGLIB$$4957273f.invoke() > at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) > at > org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:618) > at > org.apache.kylin.rest.service.QueryService$$EnhancerByCGLIB$$315e2079.query() > at > org.apache.kylin.rest.controller.QueryController.doQueryWithCache(QueryController.java:192) > at > org.apache.kylin.rest.controller.QueryController.query(QueryController.java:94) > Caused by: java.lang.ArrayIndexOutOfBoundsException: 19 > at > org.apache.kylin.dict.lookup.LookupStringTable.convertRow(LookupStringTable.java:85) > at >
[jira] [Comment Edited] (KYLIN-2106) UI bug - Advanced Settings - Rowkeys - new Integer dictionary encoding - could possibly impact also cube metadata
[ https://issues.apache.org/jira/browse/KYLIN-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15605018#comment-15605018 ] Zhong,Jason edited comment on KYLIN-2106 at 10/25/16 12:25 PM: --- [~cal...@gmail.com] Hi Richard, thank you for reporting this bug. I have just fixed this. will fixed in new release version. https://github.com/apache/kylin/commit/85717fe33712fe1b0f6d78e371aa9194ce5f1d4a was (Author: zhongjian): [~cal...@gmail.com] Hi Richard, thank you for reporting this bug. I have just fixed this. will fixed in new release version. https://github.com/apache/kylin/commit/7a25294f0b7d31c583f923b191130780ef731dd8 > UI bug - Advanced Settings - Rowkeys - new Integer dictionary encoding - > could possibly impact also cube metadata > - > > Key: KYLIN-2106 > URL: https://issues.apache.org/jira/browse/KYLIN-2106 > Project: Kylin > Issue Type: Bug > Components: Job Engine, Web >Affects Versions: v1.5.4.1 >Reporter: Richard Calaba >Assignee: Zhong,Jason > > I have realized possib,e bug in UI, to reproduce: > 1) Create Cube which has in Advance Settings - Rowkeys section a encoding of > one of the dimension (in my case it was 1st dimension - customer_id) set > encoding to 'Integer' - I used length 22. (Do not use the 'Int' Deprecated) > 2) Save this cube. > 3) Clone this cube > 4) The cloned cube had the same dimension in the Rowkeys section in Edit mode > marked as 'Int(deprecated)' and the length of the Int dictionary encoding was > set to 'ger' - obviously some issue while parsing the new Encoding type - > hopefully only on UI ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2106) UI bug - Advanced Settings - Rowkeys - new Integer dictionary encoding - could possibly impact also cube metadata
[ https://issues.apache.org/jira/browse/KYLIN-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15605018#comment-15605018 ] Zhong,Jason commented on KYLIN-2106: [~cal...@gmail.com] Hi Richard, thank you for reporting this bug. I have just fixed this. will fixed in new release version. https://github.com/apache/kylin/commit/7a25294f0b7d31c583f923b191130780ef731dd8 > UI bug - Advanced Settings - Rowkeys - new Integer dictionary encoding - > could possibly impact also cube metadata > - > > Key: KYLIN-2106 > URL: https://issues.apache.org/jira/browse/KYLIN-2106 > Project: Kylin > Issue Type: Bug > Components: Job Engine, Web >Affects Versions: v1.5.4.1 >Reporter: Richard Calaba >Assignee: Zhong,Jason > > I have realized possib,e bug in UI, to reproduce: > 1) Create Cube which has in Advance Settings - Rowkeys section a encoding of > one of the dimension (in my case it was 1st dimension - customer_id) set > encoding to 'Integer' - I used length 22. (Do not use the 'Int' Deprecated) > 2) Save this cube. > 3) Clone this cube > 4) The cloned cube had the same dimension in the Rowkeys section in Edit mode > marked as 'Int(deprecated)' and the length of the Int dictionary encoding was > set to 'ger' - obviously some issue while parsing the new Encoding type - > hopefully only on UI ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KYLIN-2078) Can't see generated SQL at Web UI
[
https://issues.apache.org/jira/browse/KYLIN-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaofeng SHI resolved KYLIN-2078.
-
Resolution: Fixed
> Can't see generated SQL at Web UI
> -
>
> Key: KYLIN-2078
> URL: https://issues.apache.org/jira/browse/KYLIN-2078
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v1.5.4, v1.5.4.1
>Reporter: Dayue Gao
>Assignee: Shaofeng SHI
> Fix For: v1.6.0
>
>
> After KYLIN-1966, user can't see generated SQL at cube page.
> {noformat}
> 2016-10-10 15:45:17,975 ERROR [http-bio-8080-exec-13]
> controller.BasicController:44 :
> java.lang.NullPointerException
> at
> org.apache.kylin.engine.EngineFactory.batchEngine(EngineFactory.java:44)
> at
> org.apache.kylin.engine.EngineFactory.getJoinedFlatTableDesc(EngineFactory.java:58)
> at
> org.apache.kylin.rest.controller.CubeController.getSql(CubeController.java:155)
> {noformat}
> Seems segmentName passed into CubeController#getSql is always null, should
> use `EngineFactory.getJoinedFlatTableDesc(cube.getDescriptor())` instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KYLIN-2114) WEB-Global-Dictionary bug fix and improve
[ https://issues.apache.org/jira/browse/KYLIN-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15604818#comment-15604818 ] liyang commented on KYLIN-2114: --- [~zhongjian] you want to review? > WEB-Global-Dictionary bug fix and improve > - > > Key: KYLIN-2114 > URL: https://issues.apache.org/jira/browse/KYLIN-2114 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.5.4.1 >Reporter: kangkaisen >Assignee: kangkaisen > Attachments: KYLIN-2114.patch > > > in the 1.5.4.1 version of Kylin, the web UI for WEB-Global-Dictionary > couldn't select column from measure columns and need user to input the > dictionary builder class manually. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2120) kylin1.5.4.1 with cdh5.7 cube sql Oops Faild to take action
[ https://issues.apache.org/jira/browse/KYLIN-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15604696#comment-15604696 ] fanshengliang commented on KYLIN-2120: -- java.lang.NullPointerException at ora.apache.kylin.engine.EngineFactory.batchEngine(EngineFactory.java:44) ora.apache.kylin.engine.EngineFactory.getJoinedFlatTableDesc(EngineFactory.java:58) > kylin1.5.4.1 with cdh5.7 cube sql Oops Faild to take action > --- > > Key: KYLIN-2120 > URL: https://issues.apache.org/jira/browse/KYLIN-2120 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: fanshengliang >Assignee: Zhong,Jason > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (KYLIN-1820) Column autocomplete should remove the user input in model designer
[ https://issues.apache.org/jira/browse/KYLIN-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong,Jason reopened KYLIN-1820: > Column autocomplete should remove the user input in model designer > -- > > Key: KYLIN-1820 > URL: https://issues.apache.org/jira/browse/KYLIN-1820 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.5.2 > Environment: OS:Mac > Safari/Chrome >Reporter: Billy(Yiming) Liu >Assignee: Zhong,Jason >Priority: Minor > Fix For: Backlog > > > In step 3 add column dimension in Model Designer, user enters the column name > and the column name autocompletion pops up. When some item is selected, the > column name shows in the textbox. At this time, the selected column should > replace the user input, not insert before the user input. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2078) Can't see generated SQL at Web UI
[
https://issues.apache.org/jira/browse/KYLIN-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15604642#comment-15604642
]
Shaofeng SHI commented on KYLIN-2078:
-
Commit:
https://github.com/apache/kylin/commit/9acc20e46c9cf83e65edc21d0d8cdf037894209d
> Can't see generated SQL at Web UI
> -
>
> Key: KYLIN-2078
> URL: https://issues.apache.org/jira/browse/KYLIN-2078
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v1.5.4, v1.5.4.1
>Reporter: Dayue Gao
>Assignee: Shaofeng SHI
> Fix For: v1.6.0
>
>
> After KYLIN-1966, user can't see generated SQL at cube page.
> {noformat}
> 2016-10-10 15:45:17,975 ERROR [http-bio-8080-exec-13]
> controller.BasicController:44 :
> java.lang.NullPointerException
> at
> org.apache.kylin.engine.EngineFactory.batchEngine(EngineFactory.java:44)
> at
> org.apache.kylin.engine.EngineFactory.getJoinedFlatTableDesc(EngineFactory.java:58)
> at
> org.apache.kylin.rest.controller.CubeController.getSql(CubeController.java:155)
> {noformat}
> Seems segmentName passed into CubeController#getSql is always null, should
> use `EngineFactory.getJoinedFlatTableDesc(cube.getDescriptor())` instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
