[jira] [Created] (KYLIN-3143) Wrong use of Preconditions.checkNotNull() in ManagedUser#removeAuthoritie
Ted Yu created KYLIN-3143:
-
Summary: Wrong use of Preconditions.checkNotNull() in
ManagedUser#removeAuthoritie
Key: KYLIN-3143
URL: https://issues.apache.org/jira/browse/KYLIN-3143
Project: Kylin
Issue Type: Bug
Reporter: Ted Yu
Priority: Minor
{code}
public void removeAuthoritie(String auth) {
Preconditions.checkNotNull(this.authorities == null);
{code}
I think the intention was to check this.authorities, not {{this.authorities ==
null}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KYLIN-2990) Add warning window of exist model names for other project selected
[ https://issues.apache.org/jira/browse/KYLIN-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307337#comment-16307337 ] liyang commented on KYLIN-2990: --- Note I reverted the check-dup logic in ModelService. Many direct REST API calls still relies on it. Please check if this impact the wanted behavior under this JIRA. > Add warning window of exist model names for other project selected > -- > > Key: KYLIN-2990 > URL: https://issues.apache.org/jira/browse/KYLIN-2990 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: peng.jianhua >Assignee: peng.jianhua > Fix For: v2.3.0 > > Attachments: > 0001-KYLIN-2990-Add-warning-window-of-exist-model-names-f.patch, 01.PNG, > 02.PNG, 03.PNG > > > I noticed that when we intend to build a new model and named it as > 'kylin_sales_model' in project 'learn_kylin'. > we will get the prompt like 01.png. > Cause we have already own the same name model. > But if we build the same name model 'kylin_sales_model' in another project > such as project_1, > we can't get the warning prompt until the last step. please refer to 02.png. > I found that we just check the model in the selected project not all project. > It's improper that we recognize the minor mistake until the final step,and we > should change the name in the first step and click 'next' buttun four times. > We should offer the same prompt for other projects. > So I modify the code in 'modelSchema.js',we can get the prompt in the first > step,please refer to 03.png. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2726) Introduce a dashboard for showing kylin service related metrics, like query count, query latency, job count, etc
[
https://issues.apache.org/jira/browse/KYLIN-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307338#comment-16307338
]
liyang commented on KYLIN-2726:
---
FYI, I reverted the {{QueryService.queryWithoutSecure()}} during a big code
merge.
https://github.com/apache/kylin/commit/4d50b26972bb7bbaff852172990e0f189f987673
The question is can we achieve the same in a secured way?
> Introduce a dashboard for showing kylin service related metrics, like query
> count, query latency, job count, etc
>
>
> Key: KYLIN-2726
> URL: https://issues.apache.org/jira/browse/KYLIN-2726
> Project: Kylin
> Issue Type: New Feature
>Reporter: Zhong Yanghong
>Assignee: Pan, Julian
> Fix For: v2.3.0
>
>
> Dashboard shows query count, query latency, job count with many dimensions,
> like server level, project level, cube level, different time granularity
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KYLIN-2764) Build the dict for UHC column with MR
[ https://issues.apache.org/jira/browse/KYLIN-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307336#comment-16307336 ] liyang commented on KYLIN-2764: --- Note I have renamed the config to "kylin.engine.mr.build-uhc-dict-in-additional-step" for better readability. FYI. > Build the dict for UHC column with MR > - > > Key: KYLIN-2764 > URL: https://issues.apache.org/jira/browse/KYLIN-2764 > Project: Kylin > Issue Type: Improvement > Components: Job Engine >Affects Versions: v2.0.0 >Reporter: kangkaisen >Assignee: kangkaisen > Fix For: v2.3.0 > > Attachments: job-memory-after.png, job-memory-before.png > > > KYLIN-2217 has built dict for normal column with MR, but the UHC column > still build dict in JobServer. Like KYLIN-2217, we also could use MR build > dict for UHC column. which could thoroughly release the memory pressure and > improve job concurrent for JobServer as well as speed up multi UHC columns > procedure. > The MR input is the output of "Extract Fact Table Distinct Columns", the MR > output is the UHC column dict. Because it is very hard build global dict with > multi reducers, I use one reducer handle one UHC column and allocate enough > memory to the reducer. According to my test, 8G memory is enough. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (KYLIN-2764) Build the dict for UHC column with MR
[ https://issues.apache.org/jira/browse/KYLIN-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307336#comment-16307336 ] liyang edited comment on KYLIN-2764 at 1/1/18 12:17 AM: Note I have renamed the config to "kylin.engine.mr.build-uhc-dict-in-additional-step" for better readability. The last chance before 2.3.0 releases. FYI. was (Author: liyang.g...@gmail.com): Note I have renamed the config to "kylin.engine.mr.build-uhc-dict-in-additional-step" for better readability. FYI. > Build the dict for UHC column with MR > - > > Key: KYLIN-2764 > URL: https://issues.apache.org/jira/browse/KYLIN-2764 > Project: Kylin > Issue Type: Improvement > Components: Job Engine >Affects Versions: v2.0.0 >Reporter: kangkaisen >Assignee: kangkaisen > Fix For: v2.3.0 > > Attachments: job-memory-after.png, job-memory-before.png > > > KYLIN-2217 has built dict for normal column with MR, but the UHC column > still build dict in JobServer. Like KYLIN-2217, we also could use MR build > dict for UHC column. which could thoroughly release the memory pressure and > improve job concurrent for JobServer as well as speed up multi UHC columns > procedure. > The MR input is the output of "Extract Fact Table Distinct Columns", the MR > output is the UHC column dict. Because it is very hard build global dict with > multi reducers, I use one reducer handle one UHC column and allocate enough > memory to the reducer. According to my test, 8G memory is enough. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2723) Introduce metrics collector for query & job metrics
[ https://issues.apache.org/jira/browse/KYLIN-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307334#comment-16307334 ] liyang commented on KYLIN-2723: --- FYI. I have renamed config "kylin.core.metrics.xxx" to "kylin.metrics.xxx" for consistency. > Introduce metrics collector for query & job metrics > --- > > Key: KYLIN-2723 > URL: https://issues.apache.org/jira/browse/KYLIN-2723 > Project: Kylin > Issue Type: Sub-task >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong > Fix For: v2.3.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-3022) Add clone() for ISegment, which is needed when updating cube segment
[ https://issues.apache.org/jira/browse/KYLIN-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307328#comment-16307328 ] liyang commented on KYLIN-3022: --- Many issues (if not all) in KYLIN-3022 has been resolved by KYLIN-3085, which requires a clone at cube level before update. Sorry, but KYLIN-3022 may need a rework. > Add clone() for ISegment, which is needed when updating cube segment > > > Key: KYLIN-3022 > URL: https://issues.apache.org/jira/browse/KYLIN-3022 > Project: Kylin > Issue Type: Improvement >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong > Attachments: APACHE-KYLIN-3022.patch > > > We should not update the memory state until the storage state is updated. > Otherwise when it fails to update the storage state, inconsistency issue will > occur. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2986) Segments overlap issue may happen when concurrent merge or build
[ https://issues.apache.org/jira/browse/KYLIN-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307327#comment-16307327 ] liyang commented on KYLIN-2986: --- Yes [~yaho], I just merged https://issues.apache.org/jira/browse/KYLIN-3085 Many issues (if not all) in KYLIN-3022 has been resolved by KYLIN-3085, which requires a clone at cube level before update. Sorry, but KYLIN-3022 may need a rework. > Segments overlap issue may happen when concurrent merge or build > > > Key: KYLIN-2986 > URL: https://issues.apache.org/jira/browse/KYLIN-2986 > Project: Kylin > Issue Type: Bug >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong >Priority: Trivial > Labels: scope > Attachments: APACHE-KYLIN-2986.patch, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-3059) Query got IllegalArgumentException
[
https://issues.apache.org/jira/browse/KYLIN-3059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307324#comment-16307324
]
liyang commented on KYLIN-3059:
---
With https://issues.apache.org/jira/browse/KYLIN-3092
I think this issue should be eased, though cannot verify since it cannot
reproduce stably.
> Query got IllegalArgumentException
> --
>
> Key: KYLIN-3059
> URL: https://issues.apache.org/jira/browse/KYLIN-3059
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Affects Versions: v1.6.0
> Environment: apache-kylin-1.6.0-hbase1.x
> apache hadoop 2.7.2
> hbase-1.2.4
>Reporter: Xingxing Di
>Assignee: liyang
> Attachments: query.log
>
>
> A query got an exception , the error trace was :
> {code:java}
> Caused by: java.lang.IllegalArgumentException
> at
> com.google.common.base.Preconditions.checkArgument(Preconditions.java:76)
> at
> org.apache.kylin.metadata.model.TblColRef.(TblColRef.java:105)
> at
> org.apache.kylin.metadata.model.TblColRef.columnForUnknownModel(TblColRef.java:74)
> at
> org.apache.kylin.query.relnode.OLAPTableScan.buildColumnRowType(OLAPTableScan.java:231)
> {code}
> the code is :
> {code:java}
> TblColRef(TableRef table, ColumnDesc column) {
> checkArgument(table.getTableDesc() == column.getTable()); // this
> line cause exception
> this.table = table;
> this.column = column;
> }
> {code}
> and after we did "Reload metadata", query executed successful.
> I dont know what will cause this exception, i think it may related to
> ProjectL2Cache or ProjectManager.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (KYLIN-3125) Support SparkSql in Cube building step "Create Intermediate Flat Hive Table"
[ https://issues.apache.org/jira/browse/KYLIN-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyang resolved KYLIN-3125. --- Resolution: Fixed Fix Version/s: v2.3.0 > Support SparkSql in Cube building step "Create Intermediate Flat Hive Table" > > > Key: KYLIN-3125 > URL: https://issues.apache.org/jira/browse/KYLIN-3125 > Project: Kylin > Issue Type: Improvement >Reporter: liyang >Assignee: liyang > Fix For: v2.3.0 > > > It is said that SparkSQL is much faster then Hive when used to create flat > table. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-3125) Support SparkSql in Cube building step "Create Intermediate Flat Hive Table"
[ https://issues.apache.org/jira/browse/KYLIN-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307320#comment-16307320 ] liyang commented on KYLIN-3125: --- Code merge done. https://github.com/apache/kylin/commit/4d50b26972bb7bbaff852172990e0f189f987673 > Support SparkSql in Cube building step "Create Intermediate Flat Hive Table" > > > Key: KYLIN-3125 > URL: https://issues.apache.org/jira/browse/KYLIN-3125 > Project: Kylin > Issue Type: Improvement >Reporter: liyang >Assignee: liyang > > It is said that SparkSQL is much faster then Hive when used to create flat > table. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-3092) Synchronize read/write operations on Managers
[ https://issues.apache.org/jira/browse/KYLIN-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyang updated KYLIN-3092: -- Description: To prevent abnormal behavior when reading cache (those getXXX methods) and writing cache (broadcast reload) happens at the same time in managers. > Synchronize read/write operations on Managers > - > > Key: KYLIN-3092 > URL: https://issues.apache.org/jira/browse/KYLIN-3092 > Project: Kylin > Issue Type: Improvement >Reporter: liyang >Assignee: liyang > Fix For: v2.3.0 > > > To prevent abnormal behavior when reading cache (those getXXX methods) and > writing cache (broadcast reload) happens at the same time in managers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-3092) Synchronize read/write operations on Managers
[ https://issues.apache.org/jira/browse/KYLIN-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307319#comment-16307319 ] liyang commented on KYLIN-3092: --- Code merge done. https://github.com/apache/kylin/commit/4d50b26972bb7bbaff852172990e0f189f987673 > Synchronize read/write operations on Managers > - > > Key: KYLIN-3092 > URL: https://issues.apache.org/jira/browse/KYLIN-3092 > Project: Kylin > Issue Type: Improvement >Reporter: liyang >Assignee: liyang > Fix For: v2.3.0 > > > To prevent abnormal behavior when reading cache (those getXXX methods) and > writing cache (broadcast reload) happens at the same time in managers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-3092) Synchronize read/write operations on Managers
[ https://issues.apache.org/jira/browse/KYLIN-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyang resolved KYLIN-3092. --- Resolution: Fixed Assignee: liyang Fix Version/s: v2.3.0 > Synchronize read/write operations on Managers > - > > Key: KYLIN-3092 > URL: https://issues.apache.org/jira/browse/KYLIN-3092 > Project: Kylin > Issue Type: Improvement >Reporter: liyang >Assignee: liyang > Fix For: v2.3.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-3090) Refactor to consolidate all caches and managers under KylinConfig
[ https://issues.apache.org/jira/browse/KYLIN-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyang resolved KYLIN-3090. --- Resolution: Fixed Assignee: liyang Fix Version/s: v2.3.0 > Refactor to consolidate all caches and managers under KylinConfig > - > > Key: KYLIN-3090 > URL: https://issues.apache.org/jira/browse/KYLIN-3090 > Project: Kylin > Issue Type: Improvement >Reporter: liyang >Assignee: liyang > Fix For: v2.3.0 > > > Refactor to consolidate all caches and managers under KylinConfig. > Such that there is a single place to clear (and GC) all cache under a > KylinConfig. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-3090) Refactor to consolidate all caches and managers under KylinConfig
[ https://issues.apache.org/jira/browse/KYLIN-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307316#comment-16307316 ] liyang commented on KYLIN-3090: --- Code merge done. https://github.com/apache/kylin/commit/4d50b26972bb7bbaff852172990e0f189f987673 > Refactor to consolidate all caches and managers under KylinConfig > - > > Key: KYLIN-3090 > URL: https://issues.apache.org/jira/browse/KYLIN-3090 > Project: Kylin > Issue Type: Improvement >Reporter: liyang > > Refactor to consolidate all caches and managers under KylinConfig. > Such that there is a single place to clear (and GC) all cache under a > KylinConfig. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-3085) CubeManager.updateCube() must not update the cached CubeInstance
[ https://issues.apache.org/jira/browse/KYLIN-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyang resolved KYLIN-3085. --- Resolution: Fixed Fix Version/s: v2.3.0 > CubeManager.updateCube() must not update the cached CubeInstance > > > Key: KYLIN-3085 > URL: https://issues.apache.org/jira/browse/KYLIN-3085 > Project: Kylin > Issue Type: Bug >Reporter: liyang >Assignee: liyang > Fix For: v2.3.0 > > > Currently CubeManager.updateCube() modifies the pass-in CubeInstance which is > the cache shared object. Causes metadata inconsistency during the period of > update, and may leave dirty metadata in memory if update fails. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-3085) CubeManager.updateCube() must not update the cached CubeInstance
[ https://issues.apache.org/jira/browse/KYLIN-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307315#comment-16307315 ] liyang commented on KYLIN-3085: --- Code merge done. https://github.com/apache/kylin/commit/4d50b26972bb7bbaff852172990e0f189f987673 > CubeManager.updateCube() must not update the cached CubeInstance > > > Key: KYLIN-3085 > URL: https://issues.apache.org/jira/browse/KYLIN-3085 > Project: Kylin > Issue Type: Bug >Reporter: liyang >Assignee: liyang > > Currently CubeManager.updateCube() modifies the pass-in CubeInstance which is > the cache shared object. Causes metadata inconsistency during the period of > update, and may leave dirty metadata in memory if update fails. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-3040) Refresh a non-partitioned cube changes the segment name to "19700101000000_2922789940817071255"
[ https://issues.apache.org/jira/browse/KYLIN-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307314#comment-16307314 ] liyang commented on KYLIN-3040: --- Code merge done. https://github.com/apache/kylin/commit/4d50b26972bb7bbaff852172990e0f189f987673 > Refresh a non-partitioned cube changes the segment name to > "1970010100_2922789940817071255" > --- > > Key: KYLIN-3040 > URL: https://issues.apache.org/jira/browse/KYLIN-3040 > Project: Kylin > Issue Type: Bug >Reporter: liyang >Assignee: liyang > Fix For: v2.3.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-3040) Refresh a non-partitioned cube changes the segment name to "19700101000000_2922789940817071255"
[ https://issues.apache.org/jira/browse/KYLIN-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyang resolved KYLIN-3040. --- Resolution: Fixed > Refresh a non-partitioned cube changes the segment name to > "1970010100_2922789940817071255" > --- > > Key: KYLIN-3040 > URL: https://issues.apache.org/jira/browse/KYLIN-3040 > Project: Kylin > Issue Type: Bug >Reporter: liyang >Assignee: liyang > Fix For: v2.3.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-3040) Refresh a non-partitioned cube changes the segment name to "19700101000000_2922789940817071255"
[ https://issues.apache.org/jira/browse/KYLIN-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyang updated KYLIN-3040: -- Fix Version/s: v2.3.0 > Refresh a non-partitioned cube changes the segment name to > "1970010100_2922789940817071255" > --- > > Key: KYLIN-3040 > URL: https://issues.apache.org/jira/browse/KYLIN-3040 > Project: Kylin > Issue Type: Bug >Reporter: liyang >Assignee: liyang > Fix For: v2.3.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2991) Query hit NumberFormatException if partitionDateFormat is not yyyy-MM-dd
[
https://issues.apache.org/jira/browse/KYLIN-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liyang resolved KYLIN-2991.
---
Resolution: Fixed
> Query hit NumberFormatException if partitionDateFormat is not -MM-dd
>
>
> Key: KYLIN-2991
> URL: https://issues.apache.org/jira/browse/KYLIN-2991
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Affects Versions: v2.2.0
>Reporter: liyang
>Assignee: liyang
> Fix For: v2.3.0
>
>
> For example, partition date column is {{MONTH_ID}}, partition date format is
> {{MMdd}}, query can hit following exception:
> {Code}
> Caused by: java.lang.NumberFormatException: For input string: "2016-01-01"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Long.parseLong(Long.java:589)
> at java.lang.Long.parseLong(Long.java:631)
> at org.apache.kylin.dimension.IntegerDimEnc.encode(IntegerDimEnc.java:99)
> at
> org.apache.kylin.dimension.IntegerDimEnc$IntegerSerializer.serialize(IntegerDimEnc.java:153)
> at
> org.apache.kylin.cube.gridtable.CubeCodeSystem.encodeColumnValue(CubeCodeSystem.java:135)
> at
> org.apache.kylin.cube.gridtable.SegmentGTStartAndEnd.encodeTime(SegmentGTStartAndEnd.java:86)
> at
> org.apache.kylin.cube.gridtable.SegmentGTStartAndEnd.getSegmentStartAndEnd(SegmentGTStartAndEnd.java:51)
> at
> org.apache.kylin.storage.gtrecord.CubeScanRangePlanner.(CubeScanRangePlanner.java:114)
> at
> org.apache.kylin.storage.gtrecord.CubeSegmentScanner.(CubeSegmentScanner.java:73)
> at org.apache.kylin.storage.gtrecord.GTC
> {Code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KYLIN-2991) Query hit NumberFormatException if partitionDateFormat is not yyyy-MM-dd
[
https://issues.apache.org/jira/browse/KYLIN-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307313#comment-16307313
]
liyang commented on KYLIN-2991:
---
Code merge done.
https://github.com/apache/kylin/commit/4d50b26972bb7bbaff852172990e0f189f987673
> Query hit NumberFormatException if partitionDateFormat is not -MM-dd
>
>
> Key: KYLIN-2991
> URL: https://issues.apache.org/jira/browse/KYLIN-2991
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Affects Versions: v2.2.0
>Reporter: liyang
>Assignee: liyang
> Fix For: v2.3.0
>
>
> For example, partition date column is {{MONTH_ID}}, partition date format is
> {{MMdd}}, query can hit following exception:
> {Code}
> Caused by: java.lang.NumberFormatException: For input string: "2016-01-01"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Long.parseLong(Long.java:589)
> at java.lang.Long.parseLong(Long.java:631)
> at org.apache.kylin.dimension.IntegerDimEnc.encode(IntegerDimEnc.java:99)
> at
> org.apache.kylin.dimension.IntegerDimEnc$IntegerSerializer.serialize(IntegerDimEnc.java:153)
> at
> org.apache.kylin.cube.gridtable.CubeCodeSystem.encodeColumnValue(CubeCodeSystem.java:135)
> at
> org.apache.kylin.cube.gridtable.SegmentGTStartAndEnd.encodeTime(SegmentGTStartAndEnd.java:86)
> at
> org.apache.kylin.cube.gridtable.SegmentGTStartAndEnd.getSegmentStartAndEnd(SegmentGTStartAndEnd.java:51)
> at
> org.apache.kylin.storage.gtrecord.CubeScanRangePlanner.(CubeScanRangePlanner.java:114)
> at
> org.apache.kylin.storage.gtrecord.CubeSegmentScanner.(CubeSegmentScanner.java:73)
> at org.apache.kylin.storage.gtrecord.GTC
> {Code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KYLIN-2991) Query hit NumberFormatException if partitionDateFormat is not yyyy-MM-dd
[
https://issues.apache.org/jira/browse/KYLIN-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liyang updated KYLIN-2991:
--
Fix Version/s: v2.3.0
> Query hit NumberFormatException if partitionDateFormat is not -MM-dd
>
>
> Key: KYLIN-2991
> URL: https://issues.apache.org/jira/browse/KYLIN-2991
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Affects Versions: v2.2.0
>Reporter: liyang
>Assignee: liyang
> Fix For: v2.3.0
>
>
> For example, partition date column is {{MONTH_ID}}, partition date format is
> {{MMdd}}, query can hit following exception:
> {Code}
> Caused by: java.lang.NumberFormatException: For input string: "2016-01-01"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Long.parseLong(Long.java:589)
> at java.lang.Long.parseLong(Long.java:631)
> at org.apache.kylin.dimension.IntegerDimEnc.encode(IntegerDimEnc.java:99)
> at
> org.apache.kylin.dimension.IntegerDimEnc$IntegerSerializer.serialize(IntegerDimEnc.java:153)
> at
> org.apache.kylin.cube.gridtable.CubeCodeSystem.encodeColumnValue(CubeCodeSystem.java:135)
> at
> org.apache.kylin.cube.gridtable.SegmentGTStartAndEnd.encodeTime(SegmentGTStartAndEnd.java:86)
> at
> org.apache.kylin.cube.gridtable.SegmentGTStartAndEnd.getSegmentStartAndEnd(SegmentGTStartAndEnd.java:51)
> at
> org.apache.kylin.storage.gtrecord.CubeScanRangePlanner.(CubeScanRangePlanner.java:114)
> at
> org.apache.kylin.storage.gtrecord.CubeSegmentScanner.(CubeSegmentScanner.java:73)
> at org.apache.kylin.storage.gtrecord.GTC
> {Code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KYLIN-742) Route unsupported queries to Hive (on Spark)
[ https://issues.apache.org/jira/browse/KYLIN-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307312#comment-16307312 ] liyang commented on KYLIN-742: -- KYLIN-2515 is done. Should this be closed too? > Route unsupported queries to Hive (on Spark) > > > Key: KYLIN-742 > URL: https://issues.apache.org/jira/browse/KYLIN-742 > Project: Kylin > Issue Type: New Feature > Components: Query Engine, SparkSQL >Reporter: Luke Han >Assignee: liyang > Fix For: Future > > Attachments: 1.x-HBase1.x-KYLIN-742-update.patch, > 1.x-HBase1.x-KYLIN-742-with-review-comments-#1-update-21_09_2015.patch, > Design Documentation.pdf > > > When Kylin can't serve coming SQL, it will be better to route it to enabled > SQL on Hadoop like SparkSQL and execute there. > Then get result and return to client through Kylin server. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
