[jira] [Resolved] (KYLIN-3851) Flink cubing step : merge dictionary
[ https://issues.apache.org/jira/browse/KYLIN-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] vinoyang resolved KYLIN-3851. - Resolution: Implemented Implemented via engine-flink: 4f04060b11e20298b84978d40582c952ed41b03d > Flink cubing step : merge dictionary > > > Key: KYLIN-3851 > URL: https://issues.apache.org/jira/browse/KYLIN-3851 > Project: Kylin > Issue Type: Sub-task > Components: Flink Engine >Reporter: vinoyang >Assignee: vinoyang >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (KYLIN-4080) Project schema update event casues error reload NEW DataModelDesc
[ https://issues.apache.org/jira/browse/KYLIN-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923096#comment-16923096 ] Yaqian Zhang commented on KYLIN-4080: - Hi Yuzhang: I think what you said is correct.Are you interested in fixing it and proposing a PR? > Project schema update event casues error reload NEW DataModelDesc > - > > Key: KYLIN-4080 > URL: https://issues.apache.org/jira/browse/KYLIN-4080 > Project: Kylin > Issue Type: Bug > Components: Metadata >Affects Versions: v2.5.2 >Reporter: Yuzhang QIU >Priority: Blocker > > Hi, dear Kylin dev team: >When create new DataModelDesc, DataModelManager.createDataModelDese:246 > will temporarily add the new model name into selected project(project1) > cache, but won't persist it. The TEMPORARY ADD operation will make the model > reloading successful, rather than throw "No project found for model ..." > exception(at ProjectManager:391). >However, If there have another threads are processing "Broadcasting > update project_schema, project1", it will clean up cache of project1 and > reload it, which will reset the "TEMPORARY ADD" operation. Meanwhile, the > model saving thread has persisted the DataModelDesc and start to reload it, > but will find there have "No project for this model". > The new model can't be created again because the conflict timestamp and > can't be reloaded into cache because the abrove problem. >How do you think about this?? > >Best regards > >yuzhang -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (KYLIN-4080) Project schema update event casues error reload NEW DataModelDesc
[ https://issues.apache.org/jira/browse/KYLIN-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaqian Zhang reassigned KYLIN-4080: --- Assignee: (was: Yaqian Zhang) > Project schema update event casues error reload NEW DataModelDesc > - > > Key: KYLIN-4080 > URL: https://issues.apache.org/jira/browse/KYLIN-4080 > Project: Kylin > Issue Type: Bug > Components: Metadata >Affects Versions: v2.5.2 >Reporter: Yuzhang QIU >Priority: Blocker > > Hi, dear Kylin dev team: >When create new DataModelDesc, DataModelManager.createDataModelDese:246 > will temporarily add the new model name into selected project(project1) > cache, but won't persist it. The TEMPORARY ADD operation will make the model > reloading successful, rather than throw "No project found for model ..." > exception(at ProjectManager:391). >However, If there have another threads are processing "Broadcasting > update project_schema, project1", it will clean up cache of project1 and > reload it, which will reset the "TEMPORARY ADD" operation. Meanwhile, the > model saving thread has persisted the DataModelDesc and start to reload it, > but will find there have "No project for this model". > The new model can't be created again because the conflict timestamp and > can't be reloaded into cache because the abrove problem. >How do you think about this?? > >Best regards > >yuzhang -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [kylin] coveralls edited a comment on issue #823: KYLIN-4055 cube quey and ad-hoc query return different meta info
coveralls edited a comment on issue #823: KYLIN-4055 cube quey and ad-hoc query return different meta info URL: https://github.com/apache/kylin/pull/823#issuecomment-527783201 ## Pull Request Test Coverage Report for [Build 4976](https://coveralls.io/builds/25538234) * **0** of **2** **(0.0%)** changed or added relevant lines in **1** file are covered. * No unchanged relevant lines lost coverage. * Overall coverage increased (+**0.005%**) to **28.078%** --- | Changes Missing Coverage | Covered Lines | Changed/Added Lines | % | | :-|--||---: | | [query/src/main/java/org/apache/kylin/query/adhoc/PushDownRunnerJdbcImpl.java](https://coveralls.io/builds/25538234/source?filename=query%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fkylin%2Fquery%2Fadhoc%2FPushDownRunnerJdbcImpl.java#L162) | 0 | 2 | 0.0% | Totals | [](https://coveralls.io/builds/25538234) | | :-- | --: | | Change from base [Build 4972](https://coveralls.io/builds/25516211): | 0.005% | | Covered Lines: | 23452 | | Relevant Lines: | 83523 | --- # 💛 - [Coveralls](https://coveralls.io) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [kylin] codecov-io commented on issue #823: KYLIN-4055 cube quey and ad-hoc query return different meta info
codecov-io commented on issue #823: KYLIN-4055 cube quey and ad-hoc query return different meta info URL: https://github.com/apache/kylin/pull/823#issuecomment-528178413 # [Codecov](https://codecov.io/gh/apache/kylin/pull/823?src=pr&el=h1) Report > Merging [#823](https://codecov.io/gh/apache/kylin/pull/823?src=pr&el=desc) into [master](https://codecov.io/gh/apache/kylin/commit/42ba57f7f396f616c8b7f622ac96c2f2f7721482?src=pr&el=desc) will **increase** coverage by `<.01%`. > The diff coverage is `0%`. [](https://codecov.io/gh/apache/kylin/pull/823?src=pr&el=tree) ```diff @@ Coverage Diff @@ ## master #823 +/- ## + Coverage 25.6% 25.61% +<.01% - Complexity 6048 6049 +1 Files 1398 1398 Lines 8352383523 Branches 1170111701 + Hits 2139021396 +6 + Misses6007860074 -4 + Partials 2055 2053 -2 ``` | [Impacted Files](https://codecov.io/gh/apache/kylin/pull/823?src=pr&el=tree) | Coverage Δ | Complexity Δ | | |---|---|---|---| | [...ache/kylin/query/adhoc/PushDownRunnerJdbcImpl.java](https://codecov.io/gh/apache/kylin/pull/823/diff?src=pr&el=tree#diff-cXVlcnkvc3JjL21haW4vamF2YS9vcmcvYXBhY2hlL2t5bGluL3F1ZXJ5L2FkaG9jL1B1c2hEb3duUnVubmVySmRiY0ltcGwuamF2YQ==) | `0% <0%> (ø)` | `0 <0> (ø)` | :arrow_down: | | [.../apache/kylin/cube/cuboid/TreeCuboidScheduler.java](https://codecov.io/gh/apache/kylin/pull/823/diff?src=pr&el=tree#diff-Y29yZS1jdWJlL3NyYy9tYWluL2phdmEvb3JnL2FwYWNoZS9reWxpbi9jdWJlL2N1Ym9pZC9UcmVlQ3Vib2lkU2NoZWR1bGVyLmphdmE=) | `66.15% <0%> (+2.3%)` | `0% <0%> (ø)` | :arrow_down: | | [...che/kylin/stream/core/storage/CheckPointStore.java](https://codecov.io/gh/apache/kylin/pull/823/diff?src=pr&el=tree#diff-c3RyZWFtLWNvcmUvc3JjL21haW4vamF2YS9vcmcvYXBhY2hlL2t5bGluL3N0cmVhbS9jb3JlL3N0b3JhZ2UvQ2hlY2tQb2ludFN0b3JlLmphdmE=) | `66.66% <0%> (+3.03%)` | `22% <0%> (+1%)` | :arrow_up: | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/kylin/pull/823?src=pr&el=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Δ = absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/kylin/pull/823?src=pr&el=footer). Last update [42ba57f...c148d6e](https://codecov.io/gh/apache/kylin/pull/823?src=pr&el=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [kylin] nichunen merged pull request #824: [KYLIN-3921] Bump Flink version from 1.7.1 to 1.9.0
nichunen merged pull request #824: [KYLIN-3921] Bump Flink version from 1.7.1 to 1.9.0 URL: https://github.com/apache/kylin/pull/824 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (KYLIN-3921) Bump Flink version from 1.7.1 to 1.9.0
[ https://issues.apache.org/jira/browse/KYLIN-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16922998#comment-16922998 ] ASF subversion and git services commented on KYLIN-3921: Commit dba1242d04d941faec0fc86c23c5f5be59537b96 in kylin's branch refs/heads/engine-flink from yanghua [ https://gitbox.apache.org/repos/asf?p=kylin.git;h=dba1242 ] [KYLIN-3921] Bump Flink version from 1.7.1 to 1.9.0 > Bump Flink version from 1.7.1 to 1.9.0 > -- > > Key: KYLIN-3921 > URL: https://issues.apache.org/jira/browse/KYLIN-3921 > Project: Kylin > Issue Type: Sub-task > Components: Flink Engine >Reporter: vinoyang >Assignee: vinoyang >Priority: Major > > Flink 1.9.0 has been released, it brings many big feature. I am going to > upgrade the version of Flink for the cube engine. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (KYLIN-3921) Bump Flink version from 1.7.1 to 1.9.0
[ https://issues.apache.org/jira/browse/KYLIN-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16922997#comment-16922997 ] ASF GitHub Bot commented on KYLIN-3921: --- nichunen commented on pull request #824: [KYLIN-3921] Bump Flink version from 1.7.1 to 1.9.0 URL: https://github.com/apache/kylin/pull/824 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Bump Flink version from 1.7.1 to 1.9.0 > -- > > Key: KYLIN-3921 > URL: https://issues.apache.org/jira/browse/KYLIN-3921 > Project: Kylin > Issue Type: Sub-task > Components: Flink Engine >Reporter: vinoyang >Assignee: vinoyang >Priority: Major > > Flink 1.9.0 has been released, it brings many big feature. I am going to > upgrade the version of Flink for the cube engine. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [kylin] coveralls commented on issue #825: KYLIN-4157 When using PrepareStatement query, functions within WHERE …
coveralls commented on issue #825: KYLIN-4157 When using PrepareStatement query, functions within WHERE … URL: https://github.com/apache/kylin/pull/825#issuecomment-527904549 ## Pull Request Test Coverage Report for [Build 4975](https://coveralls.io/builds/25523743) * **0** of **7** **(0.0%)** changed or added relevant lines in **1** file are covered. * No unchanged relevant lines lost coverage. * Overall coverage increased (+**0.01%**) to **28.084%** --- | Changes Missing Coverage | Covered Lines | Changed/Added Lines | % | | :-|--||---: | | [query/src/main/java/org/apache/kylin/query/relnode/OLAPContext.java](https://coveralls.io/builds/25523743/source?filename=query%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fkylin%2Fquery%2Frelnode%2FOLAPContext.java#L321) | 0 | 7 | 0.0% | Totals | [](https://coveralls.io/builds/25523743) | | :-- | --: | | Change from base [Build 4972](https://coveralls.io/builds/25516211): | 0.01% | | Covered Lines: | 23458 | | Relevant Lines: | 83528 | --- # 💛 - [Coveralls](https://coveralls.io) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [kylin] codecov-io commented on issue #825: KYLIN-4157 When using PrepareStatement query, functions within WHERE …
codecov-io commented on issue #825: KYLIN-4157 When using PrepareStatement query, functions within WHERE … URL: https://github.com/apache/kylin/pull/825#issuecomment-527902244 # [Codecov](https://codecov.io/gh/apache/kylin/pull/825?src=pr&el=h1) Report > Merging [#825](https://codecov.io/gh/apache/kylin/pull/825?src=pr&el=desc) into [master](https://codecov.io/gh/apache/kylin/commit/42ba57f7f396f616c8b7f622ac96c2f2f7721482?src=pr&el=desc) will **increase** coverage by `<.01%`. > The diff coverage is `0%`. [](https://codecov.io/gh/apache/kylin/pull/825?src=pr&el=tree) ```diff @@ Coverage Diff @@ ## master #825 +/- ## + Coverage 25.6% 25.61% +<.01% - Complexity 6048 6049 +1 Files 1398 1398 Lines 8352383528 +5 Branches 1170111702 +1 + Hits 2139021397 +7 + Misses6007860073 -5 - Partials 2055 2058 +3 ``` | [Impacted Files](https://codecov.io/gh/apache/kylin/pull/825?src=pr&el=tree) | Coverage Δ | Complexity Δ | | |---|---|---|---| | [...va/org/apache/kylin/query/relnode/OLAPContext.java](https://codecov.io/gh/apache/kylin/pull/825/diff?src=pr&el=tree#diff-cXVlcnkvc3JjL21haW4vamF2YS9vcmcvYXBhY2hlL2t5bGluL3F1ZXJ5L3JlbG5vZGUvT0xBUENvbnRleHQuamF2YQ==) | `0% <0%> (ø)` | `0 <0> (ø)` | :arrow_down: | | [...eam/core/storage/columnar/DataSegmentFragment.java](https://codecov.io/gh/apache/kylin/pull/825/diff?src=pr&el=tree#diff-c3RyZWFtLWNvcmUvc3JjL21haW4vamF2YS9vcmcvYXBhY2hlL2t5bGluL3N0cmVhbS9jb3JlL3N0b3JhZ2UvY29sdW1uYXIvRGF0YVNlZ21lbnRGcmFnbWVudC5qYXZh) | `59.01% <0%> (+1.63%)` | `18% <0%> (+1%)` | :arrow_up: | | [.../apache/kylin/cube/cuboid/TreeCuboidScheduler.java](https://codecov.io/gh/apache/kylin/pull/825/diff?src=pr&el=tree#diff-Y29yZS1jdWJlL3NyYy9tYWluL2phdmEvb3JnL2FwYWNoZS9reWxpbi9jdWJlL2N1Ym9pZC9UcmVlQ3Vib2lkU2NoZWR1bGVyLmphdmE=) | `66.15% <0%> (+2.3%)` | `0% <0%> (ø)` | :arrow_down: | | [...ream/core/storage/columnar/ColumnarStoreCache.java](https://codecov.io/gh/apache/kylin/pull/825/diff?src=pr&el=tree#diff-c3RyZWFtLWNvcmUvc3JjL21haW4vamF2YS9vcmcvYXBhY2hlL2t5bGluL3N0cmVhbS9jb3JlL3N0b3JhZ2UvY29sdW1uYXIvQ29sdW1uYXJTdG9yZUNhY2hlLmphdmE=) | `54.65% <0%> (+3.48%)` | `8% <0%> (ø)` | :arrow_down: | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/kylin/pull/825?src=pr&el=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Δ = absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/kylin/pull/825?src=pr&el=footer). Last update [42ba57f...d158ce5](https://codecov.io/gh/apache/kylin/pull/825?src=pr&el=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [kylin] mwu3 commented on issue #825: KYLIN-4157 When using PrepareStatement query, functions within WHERE …
mwu3 commented on issue #825: KYLIN-4157 When using PrepareStatement query, functions within WHERE … URL: https://github.com/apache/kylin/pull/825#issuecomment-527890664 Already filled root cause and solution on [KYLIN-4157](https://issues.apache.org/jira/browse/KYLIN-4157) Please check that. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (KYLIN-4157) When using PrepareStatement query, functions within WHERE will cause InternalErrorException
[ https://issues.apache.org/jira/browse/KYLIN-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Wu updated KYLIN-4157: --- Description: Hi Kylin Team: I found a bug when I'm using PreparedStatement query. Let me use table KYLIN_SALES to explain the scenario. There is a SQL like: select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower case, or they just want to query data ignoring cases. So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function within the filter. When I execute this SQL on Kylin web console, it can get the right result, but when I tried to execute it by PreparedStatement query on Postman, it threw InternalErrorException. !image-2019-09-04-15-39-58-276.png!  !image-2019-09-04-15-39-52-867.png!  h2. Root Cause I debugged Kylin to find the root cause, it turns out when the filter contains function, compFilter.getColumn is null, and the compFilter.getFunction contains lower(LSTG_FORMAT_NAME), so that compFilter.getColumn().getType().isDateTimeFamily() will throw NullPointerException, that's the root cause for this 500 error.  h2. !image-2019-09-04-20-57-46-121.png! Solution I suggest to check nullable first before using compFilter.getColumn. was: Hi Kylin Team: I found a bug when I'm using PreparedStatement query. Let me use table KYLIN_SALES to explain the scenario. There is a SQL like: select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower case, or they just want to query data ignoring cases. So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function within the filter. When I execute this SQL on Kylin web console, it can get the right result, but when I tried to execute it by PreparedStatement query on Postman, it threw InternalErrorException. !image-2019-09-04-15-39-58-276.png!  !image-2019-09-04-15-39-52-867.png! Root Cause > When using PrepareStatement query, functions within WHERE will cause > InternalErrorException > --- > > Key: KYLIN-4157 > URL: https://issues.apache.org/jira/browse/KYLIN-4157 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v2.6.3 >Reporter: Marc Wu >Assignee: Marc Wu >Priority: Major > Fix For: v2.6.4 > > Attachments: image-2019-09-04-15-39-52-867.png, > image-2019-09-04-15-39-58-276.png, image-2019-09-04-20-57-46-121.png > > > Hi Kylin Team: > I found a bug when I'm using PreparedStatement query. > Let me use table KYLIN_SALES to explain the scenario. > There is a SQL like: > select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where > lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME > In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower > case, or they just want to query data ignoring cases. > So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function > within the filter. > When I execute this SQL on Kylin web console, it can get the right result, > but when I tried to execute it by PreparedStatement query on Postman, it > threw InternalErrorException. !image-2019-09-04-15-39-58-276.png! >  > !image-2019-09-04-15-39-52-867.png! >  > > h2. Root Cause > I debugged Kylin to find the root cause, it turns out when the filter > contains function, compFilter.getColumn is null, and the > compFilter.getFunction contains lower(LSTG_FORMAT_NAME), so that > compFilter.getColumn().getType().isDateTimeFamily() will throw > NullPointerException, that's the root cause for this 500 error. >  > h2. !image-2019-09-04-20-57-46-121.png! Solution > I suggest to check nullable first before using compFilter.getColumn. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (KYLIN-4157) When using PrepareStatement query, functions within WHERE will cause InternalErrorException
[ https://issues.apache.org/jira/browse/KYLIN-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Wu updated KYLIN-4157: --- Attachment: image-2019-09-04-20-57-46-121.png > When using PrepareStatement query, functions within WHERE will cause > InternalErrorException > --- > > Key: KYLIN-4157 > URL: https://issues.apache.org/jira/browse/KYLIN-4157 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v2.6.3 >Reporter: Marc Wu >Assignee: Marc Wu >Priority: Major > Fix For: v2.6.4 > > Attachments: image-2019-09-04-15-39-52-867.png, > image-2019-09-04-15-39-58-276.png, image-2019-09-04-20-57-46-121.png > > > Hi Kylin Team: > I found a bug when I'm using PreparedStatement query. > Let me use table KYLIN_SALES to explain the scenario. > There is a SQL like: > select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where > lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME > In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower > case, or they just want to query data ignoring cases. > So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function > within the filter. > When I execute this SQL on Kylin web console, it can get the right result, > but when I tried to execute it by PreparedStatement query on Postman, it > threw InternalErrorException. !image-2019-09-04-15-39-58-276.png! >  > !image-2019-09-04-15-39-52-867.png! > Root Cause -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (KYLIN-4157) When using PrepareStatement query, functions within WHERE will cause InternalErrorException
[ https://issues.apache.org/jira/browse/KYLIN-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Wu updated KYLIN-4157: --- Description: Hi Kylin Team: I found a bug when I'm using PreparedStatement query. Let me use table KYLIN_SALES to explain the scenario. There is a SQL like: select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower case, or they just want to query data ignoring cases. So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function within the filter. When I execute this SQL on Kylin web console, it can get the right result, but when I tried to execute it by PreparedStatement query on Postman, it threw InternalErrorException. !image-2019-09-04-15-39-58-276.png!  !image-2019-09-04-15-39-52-867.png! Root Cause was: Hi Kylin Team: I found a bug when I'm using PreparedStatement query. Let me use table KYLIN_SALES to explain the scenario. There is a SQL like: select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower case, or they just want to query data ignoring cases. So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function within the filter. When I execute this SQL on Kylin web console, it can get the right result, but when I tried to execute it by PreparedStatement query on Postman, it threw InternalErrorException. !image-2019-09-04-15-39-58-276.png!  !image-2019-09-04-15-39-52-867.png!  > When using PrepareStatement query, functions within WHERE will cause > InternalErrorException > --- > > Key: KYLIN-4157 > URL: https://issues.apache.org/jira/browse/KYLIN-4157 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v2.6.3 >Reporter: Marc Wu >Assignee: Marc Wu >Priority: Major > Fix For: v2.6.4 > > Attachments: image-2019-09-04-15-39-52-867.png, > image-2019-09-04-15-39-58-276.png > > > Hi Kylin Team: > I found a bug when I'm using PreparedStatement query. > Let me use table KYLIN_SALES to explain the scenario. > There is a SQL like: > select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where > lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME > In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower > case, or they just want to query data ignoring cases. > So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function > within the filter. > When I execute this SQL on Kylin web console, it can get the right result, > but when I tried to execute it by PreparedStatement query on Postman, it > threw InternalErrorException. !image-2019-09-04-15-39-58-276.png! >  > !image-2019-09-04-15-39-52-867.png! > Root Cause -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (KYLIN-4157) When using PrepareStatement query, functions within WHERE will cause InternalErrorException
[ https://issues.apache.org/jira/browse/KYLIN-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16922456#comment-16922456 ] ASF GitHub Bot commented on KYLIN-4157: --- mwu3 commented on pull request #825: KYLIN-4157 When using PrepareStatement query, functions within WHERE … URL: https://github.com/apache/kylin/pull/825 …will cause InternalErrorException This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > When using PrepareStatement query, functions within WHERE will cause > InternalErrorException > --- > > Key: KYLIN-4157 > URL: https://issues.apache.org/jira/browse/KYLIN-4157 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v2.6.3 >Reporter: Marc Wu >Assignee: Marc Wu >Priority: Major > Fix For: v2.6.4 > > Attachments: image-2019-09-04-15-39-52-867.png, > image-2019-09-04-15-39-58-276.png > > > Hi Kylin Team: > I found a bug when I'm using PreparedStatement query. > Let me use table KYLIN_SALES to explain the scenario. > There is a SQL like: > select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where > lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME > In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower > case, or they just want to query data ignoring cases. > So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function > within the filter. > When I execute this SQL on Kylin web console, it can get the right result, > but when I tried to execute it by PreparedStatement query on Postman, it > threw InternalErrorException. !image-2019-09-04-15-39-58-276.png! >  > !image-2019-09-04-15-39-52-867.png!  -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [kylin] mwu3 opened a new pull request #825: KYLIN-4157 When using PrepareStatement query, functions within WHERE …
mwu3 opened a new pull request #825: KYLIN-4157 When using PrepareStatement query, functions within WHERE … URL: https://github.com/apache/kylin/pull/825 …will cause InternalErrorException This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [kylin] asf-ci commented on issue #825: KYLIN-4157 When using PrepareStatement query, functions within WHERE …
asf-ci commented on issue #825: KYLIN-4157 When using PrepareStatement query, functions within WHERE … URL: https://github.com/apache/kylin/pull/825#issuecomment-527886740 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (KYLIN-4157) When using PrepareStatement query, functions within WHERE will cause InternalErrorException
[ https://issues.apache.org/jira/browse/KYLIN-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16922431#comment-16922431 ] Marc Wu commented on KYLIN-4157: Got it, thanks! > When using PrepareStatement query, functions within WHERE will cause > InternalErrorException > --- > > Key: KYLIN-4157 > URL: https://issues.apache.org/jira/browse/KYLIN-4157 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v2.6.3 >Reporter: Marc Wu >Assignee: Marc Wu >Priority: Major > Fix For: v2.6.4 > > Attachments: image-2019-09-04-15-39-52-867.png, > image-2019-09-04-15-39-58-276.png > > > Hi Kylin Team: > I found a bug when I'm using PreparedStatement query. > Let me use table KYLIN_SALES to explain the scenario. > There is a SQL like: > select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where > lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME > In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower > case, or they just want to query data ignoring cases. > So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function > within the filter. > When I execute this SQL on Kylin web console, it can get the right result, > but when I tried to execute it by PreparedStatement query on Postman, it > threw InternalErrorException. !image-2019-09-04-15-39-58-276.png! > Â > !image-2019-09-04-15-39-52-867.png! Â -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (KYLIN-4157) When using PrepareStatement query, functions within WHERE will cause InternalErrorException
[ https://issues.apache.org/jira/browse/KYLIN-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI reassigned KYLIN-4157: --- Assignee: Marc Wu Hi Marc, please go ahead; Github PR or git patch are all acceptable. Thank you! > When using PrepareStatement query, functions within WHERE will cause > InternalErrorException > --- > > Key: KYLIN-4157 > URL: https://issues.apache.org/jira/browse/KYLIN-4157 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v2.6.3 >Reporter: Marc Wu >Assignee: Marc Wu >Priority: Major > Fix For: v2.6.4 > > Attachments: image-2019-09-04-15-39-52-867.png, > image-2019-09-04-15-39-58-276.png > > > Hi Kylin Team: > I found a bug when I'm using PreparedStatement query. > Let me use table KYLIN_SALES to explain the scenario. > There is a SQL like: > select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where > lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME > In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower > case, or they just want to query data ignoring cases. > So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function > within the filter. > When I execute this SQL on Kylin web console, it can get the right result, > but when I tried to execute it by PreparedStatement query on Postman, it > threw InternalErrorException. !image-2019-09-04-15-39-58-276.png! > Â > !image-2019-09-04-15-39-52-867.png! Â -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (KYLIN-4157) When using PrepareStatement query, functions within WHERE will cause InternalErrorException
[ https://issues.apache.org/jira/browse/KYLIN-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoxiang Yu reassigned KYLIN-4157: --- Assignee: (was: Xiaoxiang Yu) > When using PrepareStatement query, functions within WHERE will cause > InternalErrorException > --- > > Key: KYLIN-4157 > URL: https://issues.apache.org/jira/browse/KYLIN-4157 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v2.6.3 >Reporter: Marc Wu >Priority: Major > Fix For: v2.6.4 > > Attachments: image-2019-09-04-15-39-52-867.png, > image-2019-09-04-15-39-58-276.png > > > Hi Kylin Team: > I found a bug when I'm using PreparedStatement query. > Let me use table KYLIN_SALES to explain the scenario. > There is a SQL like: > select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where > lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME > In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower > case, or they just want to query data ignoring cases. > So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function > within the filter. > When I execute this SQL on Kylin web console, it can get the right result, > but when I tried to execute it by PreparedStatement query on Postman, it > threw InternalErrorException. !image-2019-09-04-15-39-58-276.png! > Â > !image-2019-09-04-15-39-52-867.png! Â -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (KYLIN-4157) When using PrepareStatement query, functions within WHERE will cause InternalErrorException
[ https://issues.apache.org/jira/browse/KYLIN-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoxiang Yu reassigned KYLIN-4157: --- Assignee: Xiaoxiang Yu > When using PrepareStatement query, functions within WHERE will cause > InternalErrorException > --- > > Key: KYLIN-4157 > URL: https://issues.apache.org/jira/browse/KYLIN-4157 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v2.6.3 >Reporter: Marc Wu >Assignee: Xiaoxiang Yu >Priority: Major > Fix For: v2.6.4 > > Attachments: image-2019-09-04-15-39-52-867.png, > image-2019-09-04-15-39-58-276.png > > > Hi Kylin Team: > I found a bug when I'm using PreparedStatement query. > Let me use table KYLIN_SALES to explain the scenario. > There is a SQL like: > select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where > lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME > In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower > case, or they just want to query data ignoring cases. > So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function > within the filter. > When I execute this SQL on Kylin web console, it can get the right result, > but when I tried to execute it by PreparedStatement query on Postman, it > threw InternalErrorException. !image-2019-09-04-15-39-58-276.png! > Â > !image-2019-09-04-15-39-52-867.png! Â -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (KYLIN-4157) When using PrepareStatement query, functions within WHERE will cause InternalErrorException
[ https://issues.apache.org/jira/browse/KYLIN-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16922381#comment-16922381 ] Xiaoxiang Yu commented on KYLIN-4157: - Thank you. [~mwu_] > When using PrepareStatement query, functions within WHERE will cause > InternalErrorException > --- > > Key: KYLIN-4157 > URL: https://issues.apache.org/jira/browse/KYLIN-4157 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v2.6.3 >Reporter: Marc Wu >Priority: Major > Fix For: v2.6.4 > > Attachments: image-2019-09-04-15-39-52-867.png, > image-2019-09-04-15-39-58-276.png > > > Hi Kylin Team: > I found a bug when I'm using PreparedStatement query. > Let me use table KYLIN_SALES to explain the scenario. > There is a SQL like: > select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where > lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME > In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower > case, or they just want to query data ignoring cases. > So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function > within the filter. > When I execute this SQL on Kylin web console, it can get the right result, > but when I tried to execute it by PreparedStatement query on Postman, it > threw InternalErrorException. !image-2019-09-04-15-39-58-276.png! > Â > !image-2019-09-04-15-39-52-867.png! Â -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (KYLIN-3921) Bump Flink version from 1.7.1 to 1.9.0
[ https://issues.apache.org/jira/browse/KYLIN-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16922380#comment-16922380 ] ASF GitHub Bot commented on KYLIN-3921: --- yanghua commented on pull request #824: [KYLIN-3921] Bump Flink version from 1.7.1 to 1.9.0 URL: https://github.com/apache/kylin/pull/824 JIRA ref: https://issues.apache.org/jira/browse/KYLIN-3921 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Bump Flink version from 1.7.1 to 1.9.0 > -- > > Key: KYLIN-3921 > URL: https://issues.apache.org/jira/browse/KYLIN-3921 > Project: Kylin > Issue Type: Sub-task > Components: Flink Engine >Reporter: vinoyang >Assignee: vinoyang >Priority: Major > > Flink 1.9.0 has been released, it brings many big feature. I am going to > upgrade the version of Flink for the cube engine. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [kylin] asf-ci commented on issue #824: [KYLIN-3921] Bump Flink version from 1.7.1 to 1.9.0
asf-ci commented on issue #824: [KYLIN-3921] Bump Flink version from 1.7.1 to 1.9.0 URL: https://github.com/apache/kylin/pull/824#issuecomment-527853001 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [kylin] yanghua opened a new pull request #824: [KYLIN-3921] Bump Flink version from 1.7.1 to 1.9.0
yanghua opened a new pull request #824: [KYLIN-3921] Bump Flink version from 1.7.1 to 1.9.0 URL: https://github.com/apache/kylin/pull/824 JIRA ref: https://issues.apache.org/jira/browse/KYLIN-3921 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Assigned] (KYLIN-4157) When using PrepareStatement query, functions within WHERE will cause InternalErrorException
[ https://issues.apache.org/jira/browse/KYLIN-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoxiang Yu reassigned KYLIN-4157: --- Assignee: (was: Jack) > When using PrepareStatement query, functions within WHERE will cause > InternalErrorException > --- > > Key: KYLIN-4157 > URL: https://issues.apache.org/jira/browse/KYLIN-4157 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v2.6.3 >Reporter: Marc Wu >Priority: Major > Fix For: v2.6.4 > > Attachments: image-2019-09-04-15-39-52-867.png, > image-2019-09-04-15-39-58-276.png > > > Hi Kylin Team: > I found a bug when I'm using PreparedStatement query. > Let me use table KYLIN_SALES to explain the scenario. > There is a SQL like: > select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where > lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME > In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower > case, or they just want to query data ignoring cases. > So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function > within the filter. > When I execute this SQL on Kylin web console, it can get the right result, > but when I tried to execute it by PreparedStatement query on Postman, it > threw InternalErrorException. !image-2019-09-04-15-39-58-276.png! > Â > !image-2019-09-04-15-39-52-867.png! Â -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (KYLIN-4157) When using PrepareStatement query, functions within WHERE will cause InternalErrorException
[ https://issues.apache.org/jira/browse/KYLIN-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoxiang Yu reassigned KYLIN-4157: --- Assignee: Jack > When using PrepareStatement query, functions within WHERE will cause > InternalErrorException > --- > > Key: KYLIN-4157 > URL: https://issues.apache.org/jira/browse/KYLIN-4157 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v2.6.3 >Reporter: Marc Wu >Assignee: Jack >Priority: Major > Fix For: v2.6.4 > > Attachments: image-2019-09-04-15-39-52-867.png, > image-2019-09-04-15-39-58-276.png > > > Hi Kylin Team: > I found a bug when I'm using PreparedStatement query. > Let me use table KYLIN_SALES to explain the scenario. > There is a SQL like: > select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where > lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME > In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower > case, or they just want to query data ignoring cases. > So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function > within the filter. > When I execute this SQL on Kylin web console, it can get the right result, > but when I tried to execute it by PreparedStatement query on Postman, it > threw InternalErrorException. !image-2019-09-04-15-39-58-276.png! > Â > !image-2019-09-04-15-39-52-867.png! Â -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Issue Comment Deleted] (KYLIN-3973) InvalidProtocolBufferException: Protocol message was too large. May be malicious.
[
https://issues.apache.org/jira/browse/KYLIN-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ZhouKang updated KYLIN-3973:
Comment: was deleted
(was: I think CodedInputStream's sizelimit should be seted in CubeVisitProtos. )
> InvalidProtocolBufferException: Protocol message was too large. May be
> malicious.
> --
>
> Key: KYLIN-3973
> URL: https://issues.apache.org/jira/browse/KYLIN-3973
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v2.6.1
>Reporter: Grzegorz Kołakowski
>Priority: Major
>
> For many queries I receive the following exception.
> {noformat}
> 2019-04-23 11:33:15,576 WARN [kylin-coproc--pool6-t17]
> client.SyncCoprocessorRpcChannel:54 : Call failed on IOException
> com.google.protobuf.InvalidProtocolBufferException: Protocol message was too
> large. May be malicious. Use CodedInputStream.setSizeLimit() to increase
> the size limit.
> at
> com.google.protobuf.InvalidProtocolBufferException.sizeLimitExceeded(InvalidProtocolBufferException.java:110)
> at
> com.google.protobuf.CodedInputStream.refillBuffer(CodedInputStream.java:755)
> at
> com.google.protobuf.CodedInputStream.isAtEnd(CodedInputStream.java:701)
> at
> com.google.protobuf.CodedInputStream.readTag(CodedInputStream.java:99)
> at
> org.apache.kylin.storage.hbase.cube.v2.coprocessor.endpoint.generated.CubeVisitProtos$CubeVisitResponse.(CubeVisitProtos.java:2307)
> at
> org.apache.kylin.storage.hbase.cube.v2.coprocessor.endpoint.generated.CubeVisitProtos$CubeVisitResponse.(CubeVisitProtos.java:2271)
> at
> org.apache.kylin.storage.hbase.cube.v2.coprocessor.endpoint.generated.CubeVisitProtos$CubeVisitResponse$1.parsePartialFrom(CubeVisitProtos.java:2380)
> at
> org.apache.kylin.storage.hbase.cube.v2.coprocessor.endpoint.generated.CubeVisitProtos$CubeVisitResponse$1.parsePartialFrom(CubeVisitProtos.java:2375)
> at
> org.apache.kylin.storage.hbase.cube.v2.coprocessor.endpoint.generated.CubeVisitProtos$CubeVisitResponse$Builder.mergeFrom(CubeVisitProtos.java:5101)
> at
> org.apache.kylin.storage.hbase.cube.v2.coprocessor.endpoint.generated.CubeVisitProtos$CubeVisitResponse$Builder.mergeFrom(CubeVisitProtos.java:4949)
> at
> com.google.protobuf.AbstractMessage$Builder.mergeFrom(AbstractMessage.java:337)
> at
> com.google.protobuf.AbstractMessage$Builder.mergeFrom(AbstractMessage.java:267)
> at
> com.google.protobuf.AbstractMessageLite$Builder.mergeFrom(AbstractMessageLite.java:210)
> at
> com.google.protobuf.AbstractMessage$Builder.mergeFrom(AbstractMessage.java:904)
> at
> com.google.protobuf.AbstractMessage$Builder.mergeFrom(AbstractMessage.java:267)
> at
> org.apache.hadoop.hbase.ipc.CoprocessorRpcUtils.getResponse(CoprocessorRpcUtils.java:141)
> at
> org.apache.hadoop.hbase.client.RegionCoprocessorRpcChannel.callExecService(RegionCoprocessorRpcChannel.java:94)
> at
> org.apache.hadoop.hbase.client.SyncCoprocessorRpcChannel.callMethod(SyncCoprocessorRpcChannel.java:52)
> at
> org.apache.kylin.storage.hbase.cube.v2.coprocessor.endpoint.generated.CubeVisitProtos$CubeVisitService$Stub.visitCube(CubeVisitProtos.java:5616)
> at
> org.apache.kylin.storage.hbase.cube.v2.CubeHBaseEndpointRPC$1$1.call(CubeHBaseEndpointRPC.java:246)
> at
> org.apache.kylin.storage.hbase.cube.v2.CubeHBaseEndpointRPC$1$1.call(CubeHBaseEndpointRPC.java:242)
> at org.apache.hadoop.hbase.client.HTable$12.call(HTable.java:1012)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> I use lz4 compression algorithm in HBase.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (KYLIN-4157) When using PrepareStatement query, functions within WHERE will cause InternalErrorException
[ https://issues.apache.org/jira/browse/KYLIN-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Wu updated KYLIN-4157: --- Description: Hi Kylin Team: I found a bug when I'm using PreparedStatement query. Let me use table KYLIN_SALES to explain the scenario. There is a SQL like: select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower case, or they just want to query data ignoring cases. So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function within the filter. When I execute this SQL on Kylin web console, it can get the right result, but when I tried to execute it by PreparedStatement query on Postman, it threw InternalErrorException. !image-2019-09-04-15-39-58-276.png! Â !image-2019-09-04-15-39-52-867.png! Â was: Hi Kylin Team: I found a bug when I'm using PreparedStatement query. Let me use table KYLIN_SALES to explain the scenario. There is a SQL like: select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower case, or they just want to query data ignoring cases. So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function within the filter. When I execut !image-2019-09-04-15-39-58-276.png! e this SQL on Kylin web console, it can get the right result, but when I tried to execute it by PreparedStatement query on Postman, it threw InternalErrorException. Â !image-2019-09-04-15-39-52-867.png! Â > When using PrepareStatement query, functions within WHERE will cause > InternalErrorException > --- > > Key: KYLIN-4157 > URL: https://issues.apache.org/jira/browse/KYLIN-4157 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v2.6.3 >Reporter: Marc Wu >Priority: Major > Fix For: v2.6.4 > > Attachments: image-2019-09-04-15-39-52-867.png, > image-2019-09-04-15-39-58-276.png > > > Hi Kylin Team: > I found a bug when I'm using PreparedStatement query. > Let me use table KYLIN_SALES to explain the scenario. > There is a SQL like: > select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where > lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME > In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower > case, or they just want to query data ignoring cases. > So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function > within the filter. > When I execute this SQL on Kylin web console, it can get the right result, > but when I tried to execute it by PreparedStatement query on Postman, it > threw InternalErrorException. !image-2019-09-04-15-39-58-276.png! > Â > !image-2019-09-04-15-39-52-867.png! Â -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (KYLIN-4157) When using PrepareStatement query, functions within WHERE will cause InternalErrorException
[ https://issues.apache.org/jira/browse/KYLIN-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16922241#comment-16922241 ] Marc Wu commented on KYLIN-4157: I already find the root cause and tried to fix them, and it works. Can you assign this bug to me? Thanks. > When using PrepareStatement query, functions within WHERE will cause > InternalErrorException > --- > > Key: KYLIN-4157 > URL: https://issues.apache.org/jira/browse/KYLIN-4157 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v2.6.3 >Reporter: Marc Wu >Priority: Major > Fix For: v2.6.4 > > Attachments: image-2019-09-04-15-39-52-867.png, > image-2019-09-04-15-39-58-276.png > > > Hi Kylin Team: > I found a bug when I'm using PreparedStatement query. > Let me use table KYLIN_SALES to explain the scenario. > There is a SQL like: > select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where > lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME > In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower > case, or they just want to query data ignoring cases. > So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function > within the filter. > When I execut !image-2019-09-04-15-39-58-276.png! e this SQL on Kylin web > console, it can get the right result, but when I tried to execute it by > PreparedStatement query on Postman, it threw InternalErrorException. > Â > !image-2019-09-04-15-39-52-867.png! Â -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [kylin] coveralls commented on issue #823: KYLIN-4055 cube quey and ad-hoc query return different meta info
coveralls commented on issue #823: KYLIN-4055 cube quey and ad-hoc query return different meta info URL: https://github.com/apache/kylin/pull/823#issuecomment-527783201 ## Pull Request Test Coverage Report for [Build 4973](https://coveralls.io/builds/25518009) * **0** of **2** **(0.0%)** changed or added relevant lines in **1** file are covered. * No unchanged relevant lines lost coverage. * Overall coverage remained the same at **28.074%** --- | Changes Missing Coverage | Covered Lines | Changed/Added Lines | % | | :-|--||---: | | [query/src/main/java/org/apache/kylin/query/adhoc/PushDownRunnerJdbcImpl.java](https://coveralls.io/builds/25518009/source?filename=query%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fkylin%2Fquery%2Fadhoc%2FPushDownRunnerJdbcImpl.java#L162) | 0 | 2 | 0.0% | Totals | [](https://coveralls.io/builds/25518009) | | :-- | --: | | Change from base [Build 4972](https://coveralls.io/builds/25516211): | 0.0% | | Covered Lines: | 23448 | | Relevant Lines: | 83523 | --- # 💛 - [Coveralls](https://coveralls.io) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (KYLIN-4157) When using PrepareStatement query, functions within WHERE will cause InternalErrorException
[ https://issues.apache.org/jira/browse/KYLIN-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Wu updated KYLIN-4157: --- Attachment: image-2019-09-04-15-39-52-867.png > When using PrepareStatement query, functions within WHERE will cause > InternalErrorException > --- > > Key: KYLIN-4157 > URL: https://issues.apache.org/jira/browse/KYLIN-4157 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v2.6.3 >Reporter: Marc Wu >Priority: Major > Fix For: v2.6.4 > > Attachments: image-2019-09-04-15-39-52-867.png > > > Hi Kylin Team: > I found a bug when I'm using PreparedStatement query. > Let me use table KYLIN_SALES to explain the scenario. > There is a SQL like: > select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where > lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME > In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower > case, or they just want to query data ignoring cases. > So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function within > the filter. > When I execute this SQL on Kylin web console, it can get the right result, > but when I tried to execute it by PreparedStatement query on Postman, it > threw InternalErrorException. > Â -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (KYLIN-4157) When using PrepareStatement query, functions within WHERE will cause InternalErrorException
[ https://issues.apache.org/jira/browse/KYLIN-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Wu updated KYLIN-4157: --- Attachment: image-2019-09-04-15-39-58-276.png > When using PrepareStatement query, functions within WHERE will cause > InternalErrorException > --- > > Key: KYLIN-4157 > URL: https://issues.apache.org/jira/browse/KYLIN-4157 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v2.6.3 >Reporter: Marc Wu >Priority: Major > Fix For: v2.6.4 > > Attachments: image-2019-09-04-15-39-52-867.png, > image-2019-09-04-15-39-58-276.png > > > Hi Kylin Team: > I found a bug when I'm using PreparedStatement query. > Let me use table KYLIN_SALES to explain the scenario. > There is a SQL like: > select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where > lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME > In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower > case, or they just want to query data ignoring cases. > So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function within > the filter. > When I execute this SQL on Kylin web console, it can get the right result, > but when I tried to execute it by PreparedStatement query on Postman, it > threw InternalErrorException. > Â -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (KYLIN-4157) When using PrepareStatement query, functions within WHERE will cause InternalErrorException
[ https://issues.apache.org/jira/browse/KYLIN-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Wu updated KYLIN-4157: --- Description: Hi Kylin Team: I found a bug when I'm using PreparedStatement query. Let me use table KYLIN_SALES to explain the scenario. There is a SQL like: select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower case, or they just want to query data ignoring cases. So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function within the filter. When I execut !image-2019-09-04-15-39-58-276.png! e this SQL on Kylin web console, it can get the right result, but when I tried to execute it by PreparedStatement query on Postman, it threw InternalErrorException. Â !image-2019-09-04-15-39-52-867.png! Â was: Hi Kylin Team: I found a bug when I'm using PreparedStatement query. Let me use table KYLIN_SALES to explain the scenario. There is a SQL like: select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower case, or they just want to query data ignoring cases. So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function within the filter. When I execute this SQL on Kylin web console, it can get the right result, but when I tried to execute it by PreparedStatement query on Postman, it threw InternalErrorException. Â > When using PrepareStatement query, functions within WHERE will cause > InternalErrorException > --- > > Key: KYLIN-4157 > URL: https://issues.apache.org/jira/browse/KYLIN-4157 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v2.6.3 >Reporter: Marc Wu >Priority: Major > Fix For: v2.6.4 > > Attachments: image-2019-09-04-15-39-52-867.png, > image-2019-09-04-15-39-58-276.png > > > Hi Kylin Team: > I found a bug when I'm using PreparedStatement query. > Let me use table KYLIN_SALES to explain the scenario. > There is a SQL like: > select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where > lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME > In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower > case, or they just want to query data ignoring cases. > So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function > within the filter. > When I execut !image-2019-09-04-15-39-58-276.png! e this SQL on Kylin web > console, it can get the right result, but when I tried to execute it by > PreparedStatement query on Postman, it threw InternalErrorException. > Â > !image-2019-09-04-15-39-52-867.png! Â -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (KYLIN-4157) When using PrepareStatement query, functions within WHERE will cause InternalErrorException
Marc Wu created KYLIN-4157: -- Summary: When using PrepareStatement query, functions within WHERE will cause InternalErrorException Key: KYLIN-4157 URL: https://issues.apache.org/jira/browse/KYLIN-4157 Project: Kylin Issue Type: Bug Components: Query Engine Affects Versions: v2.6.3 Reporter: Marc Wu Fix For: v2.6.4 Attachments: image-2019-09-04-15-39-52-867.png Hi Kylin Team: I found a bug when I'm using PreparedStatement query. Let me use table KYLIN_SALES to explain the scenario. There is a SQL like: select LSTG_FORMAT_NAME, sum(PRICE) from KYLIN_SALES where lower(LSTG_FORMAT_NAME) = 'fp-gtc' group by LSTG_FORMAT_NAME In some cases, user doesn't know the LSTG_FORMAT_NAME is upper case or lower case, or they just want to query data ignoring cases. So assume they use lower(LSTG_FORMAT_NAME) = 'fp-gtc', it's a function within the filter. When I execute this SQL on Kylin web console, it can get the right result, but when I tried to execute it by PreparedStatement query on Postman, it threw InternalErrorException. Â -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (KYLIN-3392) Support NULL value in Sum, Max, Min Aggregation
[ https://issues.apache.org/jira/browse/KYLIN-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-3392: Fix Version/s: v2.6.4 v3.0.0 Summary: Support NULL value in Sum, Max, Min Aggregation (was: support NULL value in Sum, Max, Min Aggregation) > Support NULL value in Sum, Max, Min Aggregation > --- > > Key: KYLIN-3392 > URL: https://issues.apache.org/jira/browse/KYLIN-3392 > Project: Kylin > Issue Type: Bug >Reporter: Yifei Wu >Assignee: Yifei Wu >Priority: Major > Fix For: v3.0.0, v2.6.4 > > > It is treated as 0 when confronted with NULL value in KYLIN's basic aggregate > measure (like sum, max, min). However, to distinguish the NULL value with 0 > is very necessary. > It should be like this > *sum(null, null) = null* > *sum(null, 1) = 1* > *max(null, null) = null* > *max(null, -1) = -1* > *min(null, -1）= -1* >  in accordance with Hive and SparkSQL -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (KYLIN-4055) cube quey and ad-hoc query return different meta info
[ https://issues.apache.org/jira/browse/KYLIN-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16922209#comment-16922209 ] ASF GitHub Bot commented on KYLIN-4055: --- zhangayqian commented on pull request #823: KYLIN-4055 cube quey and ad-hoc query return different meta info URL: https://github.com/apache/kylin/pull/823 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > cube quey and ad-hoc query return different meta info > - > > Key: KYLIN-4055 > URL: https://issues.apache.org/jira/browse/KYLIN-4055 > Project: Kylin > Issue Type: Improvement >Reporter: jinguowei >Assignee: Yaqian Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [kylin] zhangayqian opened a new pull request #823: KYLIN-4055 cube quey and ad-hoc query return different meta info
zhangayqian opened a new pull request #823: KYLIN-4055 cube quey and ad-hoc query return different meta info URL: https://github.com/apache/kylin/pull/823 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [kylin] asf-ci commented on issue #823: KYLIN-4055 cube quey and ad-hoc query return different meta info
asf-ci commented on issue #823: KYLIN-4055 cube quey and ad-hoc query return different meta info URL: https://github.com/apache/kylin/pull/823#issuecomment-527772743 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Resolved] (KYLIN-3991) Provide more config options for Flink cube engine
[
https://issues.apache.org/jira/browse/KYLIN-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
vinoyang resolved KYLIN-3991.
-
Resolution: Implemented
Implemented via engine-flink: e36a27fb034606b9aea4c45578717a215616c7d8
> Provide more config options for Flink cube engine
> -
>
> Key: KYLIN-3991
> URL: https://issues.apache.org/jira/browse/KYLIN-3991
> Project: Kylin
> Issue Type: Sub-task
> Components: Flink Engine
>Reporter: vinoyang
>Assignee: vinoyang
>Priority: Major
>
> Currently, there are some key configuration options has not been exposed to
> Kylin Flink engine, e.g. {{-yn}}. So we should expose more config options.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (KYLIN-4050) Fix a CLI option parse error for FlinkMergingDictionary and some little code refactor
[
https://issues.apache.org/jira/browse/KYLIN-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
vinoyang resolved KYLIN-4050.
-
Resolution: Fixed
Fixed via engine-flink: 2650a461754386936b39bed3c5620b709e0222fa
> Fix a CLI option parse error for FlinkMergingDictionary and some little code
> refactor
> -
>
> Key: KYLIN-4050
> URL: https://issues.apache.org/jira/browse/KYLIN-4050
> Project: Kylin
> Issue Type: Sub-task
> Components: Flink Engine
>Reporter: vinoyang
>Assignee: vinoyang
>Priority: Major
>
> {code:java}
> org.apache.flink.client.program.ProgramInvocationException: The main method
> caused an error.
> at
> org.apache.flink.client.program.PackagedProgram.callMainMethod(PackagedProgram.java:546)
> at
> org.apache.flink.client.program.PackagedProgram.invokeInteractiveModeForExecution(PackagedProgram.java:421)
> at org.apache.flink.client.program.ClusterClient.run(ClusterClient.java:427)
> at
> org.apache.flink.client.cli.CliFrontend.executeProgram(CliFrontend.java:813)
> at org.apache.flink.client.cli.CliFrontend.runProgram(CliFrontend.java:287)
> at org.apache.flink.client.cli.CliFrontend.run(CliFrontend.java:213)
> at
> org.apache.flink.client.cli.CliFrontend.parseParameters(CliFrontend.java:1050)
> at
> org.apache.flink.client.cli.CliFrontend.lambda$main$11(CliFrontend.java:1126)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1692)
> at
> org.apache.flink.runtime.security.HadoopSecurityContext.runSecured(HadoopSecurityContext.java:41)
> at org.apache.flink.client.cli.CliFrontend.main(CliFrontend.java:1126)
> Caused by: java.lang.RuntimeException: error parsing args
> at
> org.apache.kylin.common.util.AbstractApplication.execute(AbstractApplication.java:40)
> at org.apache.kylin.common.util.FlinkEntry.main(FlinkEntry.java:46)
> 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.flink.client.program.PackagedProgram.callMainMethod(PackagedProgram.java:529)
> ... 12 more
> Caused by: org.apache.commons.cli.UnrecognizedOptionException: Unrecognized
> option: -enableObjectReuse
> at org.apache.commons.cli.Parser.processOption(Parser.java:383)
> at org.apache.commons.cli.Parser.parse(Parser.java:210)
> at org.apache.commons.cli.Parser.parse(Parser.java:88)
> at
> org.apache.kylin.common.util.OptionsHelper.parseOptions(OptionsHelper.java:38)
> at
> org.apache.kylin.common.util.AbstractApplication.execute(AbstractApplication.java:36)
> ... 18 more
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
