[jira] [Comment Edited] (KYLIN-3967) sum along with case expression does not work in query

2019-04-27 Thread hejian (JIRA)


[ 
https://issues.apache.org/jira/browse/KYLIN-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827835#comment-16827835
 ] 

hejian edited comment on KYLIN-3967 at 4/28/19 6:39 AM:


emmm, which setting? 'kylin.query.enable-dynamic-column' is true already, 
that's more like that it can not work only when a foreign key appears in case 
expression:

*#1* works well, but *#2* fails with a CUBE_UNMATCHED_AGGREGATION error

 
{code:java}
#1:sum(case when normal_demention='xxx' then measure_col else 0.0 end)
#2:sum(case when derived_demention='xxx' then measure_col else 0.0 end){code}
 

 


was (Author: hejian999):
emmm, which setting? 'kylin.query.enable-dynamic-column' is true already, 
that's more like that it can not work only when a foreign key appears in case 
expression:

*#1* works well, but *#2* fails with a CUBE_UNMATCHED_AGGREGATION error

 
{code:java}
#1:sum(case when derived_demention='xxx' then measure_col else 0.0 end)
#2:sum(case when normal_demention='xxx' then measure_col else 0.0 end){code}
 

 

> sum along with case expression does not work in query
> -
>
> Key: KYLIN-3967
> URL: https://issues.apache.org/jira/browse/KYLIN-3967
> Project: Kylin
>  Issue Type: Bug
>  Components: Query Engine
>Reporter: Gladson Vas
>Priority: Blocker
> Attachments: notworkingcase.jpg, workingcase.jpg
>
>
> When i try to run a query with a sum case expression combination,
> eg: select sum(case when col1<0 then 0 else col1 end ) from table 
> i get the following error:
> No realization found for OLAPContext, CUBE_UNMATCHED_AGGREGATION[FunctionDesc 
> [expression=SUM, parameter=CASE(<($8, 0), 0, $8), returnType=null]], 
> rel#36838:OLAPTableScan.OLAP.[](table=[DEFAULT, table],ctx=,fields=[0, 1, 2, 
> 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 
> 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 
> 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 
> 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 
> 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 
> 100, 101, 102, 103, 104, 105, 106]) while executing SQL: "select sum (case 
> when col1 <0 then 0 else col1 end ) from table LIMIT 5"
>  
> is there any way to support this sum case expression in the query engine?
> Also I get the same error when the sum operation is done on a column derived 
> from a case expression in a subquery.
> eg: select sum(a.col1) from (select case when col1<0 then 0 else col1 end as 
> col1 from table) a
> Thanks,
> Gladson
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KYLIN-3967) sum along with case expression does not work in query

2019-04-27 Thread hejian (JIRA)


[ 
https://issues.apache.org/jira/browse/KYLIN-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827835#comment-16827835
 ] 

hejian commented on KYLIN-3967:
---

emmm, which setting? 'kylin.query.enable-dynamic-column' is true already, 
that's more like that it can not work only when a foreign key appears in case 
expression:

*#1* works well, but *#2* fails with a CUBE_UNMATCHED_AGGREGATION error

 
{code:java}
#1:sum(case when derived_demention='xxx' then measure_col else 0.0 end)
#2:sum(case when normal_demention='xxx' then measure_col else 0.0 end){code}
 

 

> sum along with case expression does not work in query
> -
>
> Key: KYLIN-3967
> URL: https://issues.apache.org/jira/browse/KYLIN-3967
> Project: Kylin
>  Issue Type: Bug
>  Components: Query Engine
>Reporter: Gladson Vas
>Priority: Blocker
> Attachments: notworkingcase.jpg, workingcase.jpg
>
>
> When i try to run a query with a sum case expression combination,
> eg: select sum(case when col1<0 then 0 else col1 end ) from table 
> i get the following error:
> No realization found for OLAPContext, CUBE_UNMATCHED_AGGREGATION[FunctionDesc 
> [expression=SUM, parameter=CASE(<($8, 0), 0, $8), returnType=null]], 
> rel#36838:OLAPTableScan.OLAP.[](table=[DEFAULT, table],ctx=,fields=[0, 1, 2, 
> 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 
> 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 
> 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 
> 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 
> 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 
> 100, 101, 102, 103, 104, 105, 106]) while executing SQL: "select sum (case 
> when col1 <0 then 0 else col1 end ) from table LIMIT 5"
>  
> is there any way to support this sum case expression in the query engine?
> Also I get the same error when the sum operation is done on a column derived 
> from a case expression in a subquery.
> eg: select sum(a.col1) from (select case when col1<0 then 0 else col1 end as 
> col1 from table) a
> Thanks,
> Gladson
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KYLIN-3967) sum along with case expression does not work in query

2019-04-27 Thread Shaofeng SHI (JIRA)


[ 
https://issues.apache.org/jira/browse/KYLIN-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827812#comment-16827812
 ] 

Shaofeng SHI commented on KYLIN-3967:
-

I tested it in Kylin 2.6. This feature was not enabled by default, maybe you 
didn't change the setting as above?

> sum along with case expression does not work in query
> -
>
> Key: KYLIN-3967
> URL: https://issues.apache.org/jira/browse/KYLIN-3967
> Project: Kylin
>  Issue Type: Bug
>  Components: Query Engine
>Reporter: Gladson Vas
>Priority: Blocker
> Attachments: notworkingcase.jpg, workingcase.jpg
>
>
> When i try to run a query with a sum case expression combination,
> eg: select sum(case when col1<0 then 0 else col1 end ) from table 
> i get the following error:
> No realization found for OLAPContext, CUBE_UNMATCHED_AGGREGATION[FunctionDesc 
> [expression=SUM, parameter=CASE(<($8, 0), 0, $8), returnType=null]], 
> rel#36838:OLAPTableScan.OLAP.[](table=[DEFAULT, table],ctx=,fields=[0, 1, 2, 
> 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 
> 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 
> 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 
> 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 
> 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 
> 100, 101, 102, 103, 104, 105, 106]) while executing SQL: "select sum (case 
> when col1 <0 then 0 else col1 end ) from table LIMIT 5"
>  
> is there any way to support this sum case expression in the query engine?
> Also I get the same error when the sum operation is done on a column derived 
> from a case expression in a subquery.
> eg: select sum(a.col1) from (select case when col1<0 then 0 else col1 end as 
> col1 from table) a
> Thanks,
> Gladson
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KYLIN-3967) sum along with case expression does not work in query

2019-04-27 Thread hejian (JIRA)


[ 
https://issues.apache.org/jira/browse/KYLIN-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827808#comment-16827808
 ] 

hejian commented on KYLIN-3967:
---

Hi [~Shaofengshi], the case i mentioned above dose not work in v2.4.0, has it 
been supported in newer version?

> sum along with case expression does not work in query
> -
>
> Key: KYLIN-3967
> URL: https://issues.apache.org/jira/browse/KYLIN-3967
> Project: Kylin
>  Issue Type: Bug
>  Components: Query Engine
>Reporter: Gladson Vas
>Priority: Blocker
> Attachments: notworkingcase.jpg, workingcase.jpg
>
>
> When i try to run a query with a sum case expression combination,
> eg: select sum(case when col1<0 then 0 else col1 end ) from table 
> i get the following error:
> No realization found for OLAPContext, CUBE_UNMATCHED_AGGREGATION[FunctionDesc 
> [expression=SUM, parameter=CASE(<($8, 0), 0, $8), returnType=null]], 
> rel#36838:OLAPTableScan.OLAP.[](table=[DEFAULT, table],ctx=,fields=[0, 1, 2, 
> 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 
> 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 
> 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 
> 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 
> 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 
> 100, 101, 102, 103, 104, 105, 106]) while executing SQL: "select sum (case 
> when col1 <0 then 0 else col1 end ) from table LIMIT 5"
>  
> is there any way to support this sum case expression in the query engine?
> Also I get the same error when the sum operation is done on a column derived 
> from a case expression in a subquery.
> eg: select sum(a.col1) from (select case when col1<0 then 0 else col1 end as 
> col1 from table) a
> Thanks,
> Gladson
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KYLIN-3974) confused about the megering segments forcely function, can not work when there exists gaps

2019-04-27 Thread hejian (JIRA)


[ 
https://issues.apache.org/jira/browse/KYLIN-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827792#comment-16827792
 ] 

hejian commented on KYLIN-3974:
---

This issue happens when including an orphan segment, and auto deleting these 
segments before megering will be better? 

> confused about the megering segments forcely function, can not work when 
> there exists gaps
> --
>
> Key: KYLIN-3974
> URL: https://issues.apache.org/jira/browse/KYLIN-3974
> Project: Kylin
>  Issue Type: Bug
>Affects Versions: v2.4.0
>Reporter: hejian
>Priority: Major
> Attachments: image-2019-04-23-18-57-01-878.png, 
> image-2019-04-23-19-02-05-743.png, image-2019-04-23-19-02-53-396.png
>
>
> forcely
> !image-2019-04-23-19-02-05-743.png!!image-2019-04-23-19-02-53-396.png!  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (KYLIN-3964) segment overlapped, the status is "NEW", last_build_job_id is null, can not refresh/delete/build this segment

2019-04-27 Thread hejian (JIRA)


 [ 
https://issues.apache.org/jira/browse/KYLIN-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

hejian closed KYLIN-3964.
-
   Resolution: Fixed
Fix Version/s: v2.5.0

> segment overlapped, the status is "NEW", last_build_job_id is null, can not  
> refresh/delete/build this segment
> --
>
> Key: KYLIN-3964
> URL: https://issues.apache.org/jira/browse/KYLIN-3964
> Project: Kylin
>  Issue Type: Bug
> Environment: kylin-2.4.0
>Reporter: hejian
>Priority: Major
> Fix For: v2.5.0
>
> Attachments: image-2019-04-22-10-07-06-737.png, 
> image-2019-04-23-16-51-34-805.png, image-2019-04-23-16-52-55-756.png
>
>
> *Any action* *involved* *this segment can not be excute by requesting api due 
> to no job_id provided.*
> !image-2019-04-22-10-07-06-737.png!
> merge/refresh/rebuild/delete does not work 
> !image-2019-04-23-16-51-34-805.png!!image-2019-04-23-16-52-55-756.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Issue Comment Deleted] (KYLIN-3964) segment overlapped, the status is "NEW", last_build_job_id is null, can not refresh/delete/build this segment

2019-04-27 Thread hejian (JIRA)


 [ 
https://issues.apache.org/jira/browse/KYLIN-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

hejian updated KYLIN-3964:
--
Comment: was deleted

(was: [~Shaofengshi] thanks a lot, help close this issue pls.)

> segment overlapped, the status is "NEW", last_build_job_id is null, can not  
> refresh/delete/build this segment
> --
>
> Key: KYLIN-3964
> URL: https://issues.apache.org/jira/browse/KYLIN-3964
> Project: Kylin
>  Issue Type: Bug
> Environment: kylin-2.4.0
>Reporter: hejian
>Priority: Major
> Attachments: image-2019-04-22-10-07-06-737.png, 
> image-2019-04-23-16-51-34-805.png, image-2019-04-23-16-52-55-756.png
>
>
> *Any action* *involved* *this segment can not be excute by requesting api due 
> to no job_id provided.*
> !image-2019-04-22-10-07-06-737.png!
> merge/refresh/rebuild/delete does not work 
> !image-2019-04-23-16-51-34-805.png!!image-2019-04-23-16-52-55-756.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KYLIN-3964) segment overlapped, the status is "NEW", last_build_job_id is null, can not refresh/delete/build this segment

2019-04-27 Thread hejian (JIRA)


[ 
https://issues.apache.org/jira/browse/KYLIN-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827787#comment-16827787
 ] 

hejian commented on KYLIN-3964:
---

[~Shaofengshi] thanks a lot, help close this issue pls.

> segment overlapped, the status is "NEW", last_build_job_id is null, can not  
> refresh/delete/build this segment
> --
>
> Key: KYLIN-3964
> URL: https://issues.apache.org/jira/browse/KYLIN-3964
> Project: Kylin
>  Issue Type: Bug
> Environment: kylin-2.4.0
>Reporter: hejian
>Priority: Major
> Attachments: image-2019-04-22-10-07-06-737.png, 
> image-2019-04-23-16-51-34-805.png, image-2019-04-23-16-52-55-756.png
>
>
> *Any action* *involved* *this segment can not be excute by requesting api due 
> to no job_id provided.*
> !image-2019-04-22-10-07-06-737.png!
> merge/refresh/rebuild/delete does not work 
> !image-2019-04-23-16-51-34-805.png!!image-2019-04-23-16-52-55-756.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[GitHub] [kylin] coveralls commented on issue #622: KYLIN-3893 Add validation for the encoding length and the type of encoding

2019-04-27 Thread GitBox
coveralls commented on issue #622: KYLIN-3893 Add validation for the encoding 
length and the type of encoding
URL: https://github.com/apache/kylin/pull/622#issuecomment-487300031
 
 
   ## Pull Request Test Coverage Report for [Build 
4427](https://coveralls.io/builds/23062942)
   
   * **2** of **22**   **(9.09%)**  changed or added relevant lines in **2** 
files are covered.
   * **1** unchanged line in **1** file lost coverage.
   * Overall coverage decreased (**-0.003%**) to **27.812%**
   
   ---
   
   |  Changes Missing Coverage | Covered Lines | Changed/Added Lines | % |
   | :-|--||---: |
   | 
[core-cube/src/main/java/org/apache/kylin/cube/kv/CubeDimEncMap.java](https://coveralls.io/builds/23062942/source?filename=core-cube%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fkylin%2Fcube%2Fkv%2FCubeDimEncMap.java#L76)
 | 2 | 4 | 50.0%
   | 
[server-base/src/main/java/org/apache/kylin/rest/controller/CubeController.java](https://coveralls.io/builds/23062942/source?filename=server-base%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fkylin%2Frest%2Fcontroller%2FCubeController.java#L639)
 | 0 | 18 | 0.0%
   
   
   |  Files with Coverage Reduction | New Missed Lines | % |
   | :-|--|--: |
   | 
[server-base/src/main/java/org/apache/kylin/rest/controller/CubeController.java](https://coveralls.io/builds/23062942/source?filename=server-base%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fkylin%2Frest%2Fcontroller%2FCubeController.java#L665)
 | 1 | 0.0% |
   
   
   |  Totals | [![Coverage 
Status](https://coveralls.io/builds/23062942/badge)](https://coveralls.io/builds/23062942)
 |
   | :-- | --: |
   | Change from base [Build 4426](https://coveralls.io/builds/23058659): |  
-0.003% |
   | Covered Lines: | 22758 |
   | Relevant Lines: | 81829 |
   
   ---
   # 💛  - [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 #622: KYLIN-3893 Add validation for the encoding length and the type of encoding

2019-04-27 Thread GitBox
codecov-io commented on issue #622: KYLIN-3893 Add validation for the encoding 
length and the type of encoding
URL: https://github.com/apache/kylin/pull/622#issuecomment-487299929
 
 
   # [Codecov](https://codecov.io/gh/apache/kylin/pull/622?src=pr&el=h1) Report
   > Merging [#622](https://codecov.io/gh/apache/kylin/pull/622?src=pr&el=desc) 
into 
[master](https://codecov.io/gh/apache/kylin/commit/c04694bf9a7e70e7f63870157884fdcde030f88a?src=pr&el=desc)
 will **decrease** coverage by `<.01%`.
   > The diff coverage is `9.09%`.
   
   [![Impacted file tree 
graph](https://codecov.io/gh/apache/kylin/pull/622/graphs/tree.svg?width=650&token=JawVgbgsVo&height=150&src=pr)](https://codecov.io/gh/apache/kylin/pull/622?src=pr&el=tree)
   
   ```diff
   @@ Coverage Diff  @@
   ## master #622  +/-   ##
   
   - Coverage 25.33%   25.33%   -0.01% 
 Complexity 5840 5840  
   
 Files  1379 1379  
 Lines 8180881829  +21 
 Branches  1146511471   +6 
   
   + Hits  2072820732   +4 
   - Misses5905759075  +18 
   + Partials   2023 2022   -1
   ```
   
   
   | [Impacted 
Files](https://codecov.io/gh/apache/kylin/pull/622?src=pr&el=tree) | Coverage Δ 
| Complexity Δ | |
   |---|---|---|---|
   | 
[...g/apache/kylin/rest/controller/CubeController.java](https://codecov.io/gh/apache/kylin/pull/622/diff?src=pr&el=tree#diff-c2VydmVyLWJhc2Uvc3JjL21haW4vamF2YS9vcmcvYXBhY2hlL2t5bGluL3Jlc3QvY29udHJvbGxlci9DdWJlQ29udHJvbGxlci5qYXZh)
 | `0% <0%> (ø)` | `0 <0> (ø)` | :arrow_down: |
   | 
[...n/java/org/apache/kylin/cube/kv/CubeDimEncMap.java](https://codecov.io/gh/apache/kylin/pull/622/diff?src=pr&el=tree#diff-Y29yZS1jdWJlL3NyYy9tYWluL2phdmEvb3JnL2FwYWNoZS9reWxpbi9jdWJlL2t2L0N1YmVEaW1FbmNNYXAuamF2YQ==)
 | `61.29% <50%> (-3%)` | `5 <0> (ø)` | |
   | 
[.../apache/kylin/cube/cuboid/TreeCuboidScheduler.java](https://codecov.io/gh/apache/kylin/pull/622/diff?src=pr&el=tree#diff-Y29yZS1jdWJlL3NyYy9tYWluL2phdmEvb3JnL2FwYWNoZS9reWxpbi9jdWJlL2N1Ym9pZC9UcmVlQ3Vib2lkU2NoZWR1bGVyLmphdmE=)
 | `66.15% <0%> (+2.3%)` | `0% <0%> (ø)` | :arrow_down: |
   
   --
   
   [Continue to review full report at 
Codecov](https://codecov.io/gh/apache/kylin/pull/622?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/622?src=pr&el=footer). Last 
update 
[c04694b...92a45ec](https://codecov.io/gh/apache/kylin/pull/622?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] GinaZhai opened a new pull request #622: Kylin 3893 Add validation for the encoding length and the type of encoding

2019-04-27 Thread GitBox
GinaZhai opened a new pull request #622: Kylin 3893 Add validation for the 
encoding length and the type of encoding
URL: https://github.com/apache/kylin/pull/622
 
 
   


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] asfgit commented on issue #622: Kylin 3893 Add validation for the encoding length and the type of encoding

2019-04-27 Thread GitBox
asfgit commented on issue #622: Kylin 3893 Add validation for the encoding 
length and the type of encoding
URL: https://github.com/apache/kylin/pull/622#issuecomment-487297766
 
 
   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] [Updated] (KYLIN-3965) When using DriverManager - No suitable driver found for jdbc:kylin://

2019-04-27 Thread Shaofeng SHI (JIRA)


 [ 
https://issues.apache.org/jira/browse/KYLIN-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shaofeng SHI updated KYLIN-3965:

Fix Version/s: v2.6.2

> When using DriverManager - No suitable driver found for jdbc:kylin://
> -
>
> Key: KYLIN-3965
> URL: https://issues.apache.org/jira/browse/KYLIN-3965
> Project: Kylin
>  Issue Type: Bug
>  Components: Driver - JDBC
>Affects Versions: v2.6.1
>Reporter: Alexander
>Assignee: Alexander
>Priority: Minor
> Fix For: v2.6.2
>
> Attachments: KYLIN-3965.master.001.patch
>
>
> Caused by: java.sql.SQLException: No suitable driver found for jdbc:kylin://
>  
> This is because META-INF/services/java.sql.Driver got incorrect name
> org.apache.calcite.avatica.remote.Driver



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KYLIN-3989) Invalid temporary table path for kylin_metadata

2019-04-27 Thread Shaofeng SHI (JIRA)


[ 
https://issues.apache.org/jira/browse/KYLIN-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827630#comment-16827630
 ] 

Shaofeng SHI commented on KYLIN-3989:
-

Hello Frederic, Apache Kylin doesn't support MapR out-of-box. You can contact 
MapR or Kyligence to get support as they have the joint solution.

> Invalid temporary table path for kylin_metadata
> ---
>
> Key: KYLIN-3989
> URL: https://issues.apache.org/jira/browse/KYLIN-3989
> Project: Kylin
>  Issue Type: Bug
>Affects Versions: v2.5.2
> Environment: MapR 6.1
> Hive 2.3
>Reporter: Frederic Souchu
>Priority: Major
>
> How to reproduce:
>  * create a mode
>  * define a cube
>  * build the cube
> The cube building will fail with the following Hive logs:
> {code:java}
> USE default;
> No rows affected (0.067 seconds)
> 0: jdbc:hive2://x.com>
> 0: jdbc:hive2://x.com> DROP TABLE IF EXISTS 
> kylin_intermediate_txn_cube_99023bdd_79e8_1186_2480_28b1d352d09e;
> No rows affected (0.023 seconds)
> 0: jdbc:hive2://x.com> CREATE EXTERNAL TABLE IF NOT EXISTS 
> kylin_intermediate_txn_cube_99023bdd_79e8_1186_2480_28b1d352d09
> e
> . . . . . . . . . . . . . . . . . . . . . . .> (
> . . . . . . . . . . . . . . . . . . . . . . .> PAYMENTS_GLOBALMERCHANTUID int
> . . . . . . . . . . . . . . . . . . . . . . .> )
> . . . . . . . . . . . . . . . . . . . . . . .> STORED AS SEQUENCEFILE
> . . . . . . . . . . . . . . . . . . . . . . .> LOCATION 
> 'maprfs:///apps/kylin_metadata/kylin-15b76d79-29ce-5782-d84e-bd33c305fc6f/kylin_intermedia
> te_txn_cube_99023bdd_79e8_1186_2480_28b1d352d09e';
> Error: org.apache.hive.service.cli.HiveSQLException: Error while processing 
> statement: FAILED: Execution Error, return code 1 from 
> org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:Got exception: 
> java.io.IOException Error: Not a directory(20), file: 
> kylin_intermediate_txn_cube_99023bdd_79e8_1186_2480_28b1d352d09e, user name: 
> mapr, ID: 5000)
> {code}
> using metastore.sh to list content gives:
> {code}
> 2019-04-26 15:25:54,231 INFO  [main] common.KylinConfig:100 : Loading 
> kylin-defaults.properties from 
> file:/opt/apache-kylin-2.5.2-bin-hbase1x/tool/kylin-tool-2.5.2.jar!/kylin-defaults.properties
> 2019-04-26 15:25:54,257 DEBUG [main] common.KylinConfig:327 : KYLIN_CONF 
> property was not set, will seek KYLIN_HOME env variable
> 2019-04-26 15:25:54,263 INFO  [main] common.KylinConfig:135 : Initialized a 
> new KylinConfig from getInstanceFromEnv : 453523494
> 2019-04-26 15:25:54,376 INFO  [main] persistence.ResourceStore:88 : Using 
> metadata url /apps/kylin_metadata@hbase for resource store
> 2019-04-26 15:25:55,684 DEBUG [main] hbase.HBaseConnection:180 : Using the 
> working dir FS for HBase: maprfs:///
> 2019-04-26 15:25:55,684 INFO  [main] hbase.HBaseConnection:257 : connection 
> is null or closed, creating a new one
> 2019-04-26 15:25:55,719 INFO  [main] client.ConnectionFactory:272 : 
> ConnectionFactory receives mapr.hbase.default.db(maprdb), set 
> clusterType(MAPR_ONLY), user(mapr), hbase_admin_connect_at_construction(false)
> 2019-04-26 15:25:55,899 DEBUG [main] hbase.HBaseConnection:306 : HTable 
> '/apps/kylin_metadata' already exists
> null
> 2019-04-26 15:25:56,400 INFO  [close-hbase-conn] hbase.HBaseConnection:136 : 
> Closing HBase connections...
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (KYLIN-3988) Weighted Average does not work on cube

2019-04-27 Thread Shaofeng SHI (JIRA)


[ 
https://issues.apache.org/jira/browse/KYLIN-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827626#comment-16827626
 ] 

Shaofeng SHI edited comment on KYLIN-3988 at 4/27/19 2:40 PM:
--

Hello Anoop, sum(x*y) couldn't be translated to sum(X) and sum(Y) with any 
operator, so it is not supported by Kylin, unless you define a column "z" = 
"x*y" in the source table, and then define "sum(z)" as a measure. If you're not 
willing to add this column in your hive table, you can define it in a hive 
view, and then use the view as the cube fact table.


was (Author: shaofengshi):
Hello Anoop, sum(x*y) couldn't be translated to sum(x) and sum(y) with any 
operator, so it is not supported by Kylin, unless you define a column "z" = 
"x*y" in the source table, and then define "sum(z)" as a measure. If you're not 
willing to add this column in your hive table, you can define it in a hive 
view, and then use the view as the cube fact table.

> Weighted Average does not work on cube
> --
>
> Key: KYLIN-3988
> URL: https://issues.apache.org/jira/browse/KYLIN-3988
> Project: Kylin
>  Issue Type: Bug
>  Components: Driver - ODBC
>Affects Versions: v2.6.1
>Reporter: Anoop Krishnaswamy
>Priority: Critical
>
> When we try to get aggregate over multiplication of 2 metrics it throws an 
> error:
> That both of the two sides of the BinaryTupleExpression own columns is not 
> supported for * while executing SQL: "select 
> sum(riskscoreinitial*cyc_xxx_balanceAdb), cyc_xxx_cyclesdelinquent from 
> fct_profit_table_monthly group by cyc_xxx_cyclesdelinquent LIMIT 5"
>  
> My query looks something like this :
>  
> select sum(*),  from  group by 
> Any guidance will help



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KYLIN-3988) Weighted Average does not work on cube

2019-04-27 Thread Shaofeng SHI (JIRA)


[ 
https://issues.apache.org/jira/browse/KYLIN-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827626#comment-16827626
 ] 

Shaofeng SHI commented on KYLIN-3988:
-

Hello Anoop, sum(x*y) couldn't be translated to sum(x) and sum(y) with any 
operator, so it is not supported by Kylin, unless you define a column "z" = 
"x*y" in the source table, and then define "sum(z)" as a measure. If you're not 
willing to add this column in your hive table, you can define it in a hive 
view, and then use the view as the cube fact table.

> Weighted Average does not work on cube
> --
>
> Key: KYLIN-3988
> URL: https://issues.apache.org/jira/browse/KYLIN-3988
> Project: Kylin
>  Issue Type: Bug
>  Components: Driver - ODBC
>Affects Versions: v2.6.1
>Reporter: Anoop Krishnaswamy
>Priority: Critical
>
> When we try to get aggregate over multiplication of 2 metrics it throws an 
> error:
> That both of the two sides of the BinaryTupleExpression own columns is not 
> supported for * while executing SQL: "select 
> sum(riskscoreinitial*cyc_xxx_balanceAdb), cyc_xxx_cyclesdelinquent from 
> fct_profit_table_monthly group by cyc_xxx_cyclesdelinquent LIMIT 5"
>  
> My query looks something like this :
>  
> select sum(*),  from  group by 
> Any guidance will help



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KYLIN-3964) segment overlapped, the status is "NEW", last_build_job_id is null, can not refresh/delete/build this segment

2019-04-27 Thread Shaofeng SHI (JIRA)


[ 
https://issues.apache.org/jira/browse/KYLIN-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827624#comment-16827624
 ] 

Shaofeng SHI commented on KYLIN-3964:
-

[~hejian999] you can take a look at 

https://issues.apache.org/jira/browse/KYLIN-3449

It will allow delete an orphan segment (only segment, no job), which is in 
Kylin 2.5.

> segment overlapped, the status is "NEW", last_build_job_id is null, can not  
> refresh/delete/build this segment
> --
>
> Key: KYLIN-3964
> URL: https://issues.apache.org/jira/browse/KYLIN-3964
> Project: Kylin
>  Issue Type: Bug
> Environment: kylin-2.4.0
>Reporter: hejian
>Priority: Major
> Attachments: image-2019-04-22-10-07-06-737.png, 
> image-2019-04-23-16-51-34-805.png, image-2019-04-23-16-52-55-756.png
>
>
> *Any action* *involved* *this segment can not be excute by requesting api due 
> to no job_id provided.*
> !image-2019-04-22-10-07-06-737.png!
> merge/refresh/rebuild/delete does not work 
> !image-2019-04-23-16-51-34-805.png!!image-2019-04-23-16-52-55-756.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)