[jira] [Commented] (KYLIN-2249) Build cube error when use "inmem" but ok with "layer"

2016-12-06 Thread zhou degao (JIRA)

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

zhou degao commented on KYLIN-2249:
---

I got the same errors

> Build cube error when use "inmem" but ok with "layer"
> -
>
> Key: KYLIN-2249
> URL: https://issues.apache.org/jira/browse/KYLIN-2249
> Project: Kylin
>  Issue Type: Bug
>Affects Versions: v1.6.0
> Environment: CentOS
>Reporter: hoangle
>   Original Estimate: 410h
>  Remaining Estimate: 410h
>
> My cube building is ok if I set configure:
> kylin.cube.algorithm=layer
> But It always error (at Step Name: Build Cube) when I change "layer" to 
> "inmem"
>  
> 2016-12-05 17:17:37,451 ERROR [Thread-13] 
> org.apache.kylin.dict.TrieDictionary: Not a valid value: 122594010041
> 2016-12-05 17:17:38,452 ERROR [pool-8-thread-1] 
> org.apache.kylin.cube.inmemcubing.DoggedCubeBuilder: Dogged Cube Build error
> java.io.IOException: java.lang.IllegalArgumentException: Value not exists!
>   at 
> org.apache.kylin.cube.inmemcubing.DoggedCubeBuilder$BuildOnce.abort(DoggedCubeBuilder.java:196)
>   at 
> org.apache.kylin.cube.inmemcubing.DoggedCubeBuilder$BuildOnce.checkException(DoggedCubeBuilder.java:169)
>   at 
> org.apache.kylin.cube.inmemcubing.DoggedCubeBuilder$BuildOnce.build(DoggedCubeBuilder.java:116)
>   at 
> org.apache.kylin.cube.inmemcubing.DoggedCubeBuilder.build(DoggedCubeBuilder.java:75)
>   at 
> org.apache.kylin.cube.inmemcubing.AbstractInMemCubeBuilder$1.run(AbstractInMemCubeBuilder.java:82)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   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)
> Caused by: java.lang.IllegalArgumentException: Value not exists!
>   at 
> org.apache.kylin.common.util.Dictionary.getIdFromValueBytes(Dictionary.java:162)
>   at 
> org.apache.kylin.dict.TrieDictionary.getIdFromValueImpl(TrieDictionary.java:167)
>   at 
> org.apache.kylin.common.util.Dictionary.getIdFromValue(Dictionary.java:98)
>   at 
> org.apache.kylin.dimension.DictionaryDimEnc$DictionarySerializer.serialize(DictionaryDimEnc.java:121)
>   at 
> org.apache.kylin.cube.gridtable.CubeCodeSystem.encodeColumnValue(CubeCodeSystem.java:121)
>   at 
> org.apache.kylin.cube.gridtable.CubeCodeSystem.encodeColumnValue(CubeCodeSystem.java:110)
>   at org.apache.kylin.gridtable.GTRecord.setValues(GTRecord.java:93)
>   at org.apache.kylin.gridtable.GTRecord.setValues(GTRecord.java:81)
>   at 
> org.apache.kylin.cube.inmemcubing.InMemCubeBuilderInputConverter.convert(InMemCubeBuilderInputConverter.java:74)
>   at 
> org.apache.kylin.cube.inmemcubing.InMemCubeBuilder$InputConverter$1.next(InMemCubeBuilder.java:544)
>   at 
> org.apache.kylin.cube.inmemcubing.InMemCubeBuilder$InputConverter$1.next(InMemCubeBuilder.java:525)
>   at 
> org.apache.kylin.gridtable.GTAggregateScanner.iterator(GTAggregateScanner.java:139)
>   at 
> org.apache.kylin.cube.inmemcubing.InMemCubeBuilder.createBaseCuboid(InMemCubeBuilder.java:341)
>   at 
> org.apache.kylin.cube.inmemcubing.InMemCubeBuilder.build(InMemCubeBuilder.java:168)
>   at 
> org.apache.kylin.cube.inmemcubing.InMemCubeBuilder.build(InMemCubeBuilder.java:137)
>   at 
> org.apache.kylin.cube.inmemcubing.DoggedCubeBuilder$SplitThread.run(DoggedCubeBuilder.java:284)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (KYLIN-2250) Make HiveMRInput support Hive View

2016-12-06 Thread Wang Cheng (JIRA)

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

Wang Cheng closed KYLIN-2250.
-
Resolution: Fixed

> Make HiveMRInput support Hive View
> --
>
> Key: KYLIN-2250
> URL: https://issues.apache.org/jira/browse/KYLIN-2250
> Project: Kylin
>  Issue Type: Bug
>Reporter: Wang Cheng
>Priority: Minor
>
> When hive table is a view, it can not be accessed by HCatalog. A compromised 
> way is to materialize the view firstly.
> In this purpose, make a little bit changes in HiveMRInput.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (KYLIN-2182) Aggregation Group Joint Dimension generation default rule update

2016-12-06 Thread qianqiaoneng (JIRA)

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

qianqiaoneng commented on KYLIN-2182:
-

Is there any proposal here? we are thinking do it via dimension cardinality. 
like put low cardinality dimensions as joint dimensions.

> Aggregation Group Joint Dimension generation default rule update
> 
>
> Key: KYLIN-2182
> URL: https://issues.apache.org/jira/browse/KYLIN-2182
> Project: Kylin
>  Issue Type: Improvement
>Affects Versions: v1.5.4.1
>Reporter: Zhong,Jason
> Fix For: v1.6.1
>
>
> when we create cube, if we have multiple dimensions, we will split dimensions 
> into different Joint, this is not so meaningful



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (KYLIN-2182) Aggregation Group Joint Dimension generation default rule update

2016-12-06 Thread Billy Liu (JIRA)

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

Billy Liu commented on KYLIN-2182:
--

Current rule is very simple, if too many dimensions defined(more than 10), then 
the last few dimensions will be added as joint dimensions, that's why we say it 
not meaningful. Base on the dimension cardinality is better.  Could you 
continue this improvement? 

> Aggregation Group Joint Dimension generation default rule update
> 
>
> Key: KYLIN-2182
> URL: https://issues.apache.org/jira/browse/KYLIN-2182
> Project: Kylin
>  Issue Type: Improvement
>Affects Versions: v1.5.4.1
>Reporter: Zhong,Jason
> Fix For: v1.6.1
>
>
> when we create cube, if we have multiple dimensions, we will split dimensions 
> into different Joint, this is not so meaningful



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (KYLIN-2251) JDBC Driver httpcore dependency conflict

2016-12-06 Thread Billy Liu (JIRA)

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

Billy Liu commented on KYLIN-2251:
--

Will keep the httpcore same version with httpclient, which is lower than the 
dependency of avatica. 

> JDBC Driver httpcore dependency conflict
> 
>
> Key: KYLIN-2251
> URL: https://issues.apache.org/jira/browse/KYLIN-2251
> Project: Kylin
>  Issue Type: Bug
>  Components: Driver - JDBC
>Affects Versions: v1.6.0
>Reporter: Billy Liu
>Assignee: Billy Liu
>Priority: Minor
>
> Report by xwhfcenter from github:
> "There is a conflict in dependency of httpcore in module JDBC Driver"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (KYLIN-2251) JDBC Driver httpcore dependency conflict

2016-12-06 Thread Billy Liu (JIRA)
Billy Liu created KYLIN-2251:


 Summary: JDBC Driver httpcore dependency conflict
 Key: KYLIN-2251
 URL: https://issues.apache.org/jira/browse/KYLIN-2251
 Project: Kylin
  Issue Type: Bug
  Components: Driver - JDBC
Affects Versions: v1.6.0
Reporter: Billy Liu
Assignee: Billy Liu
Priority: Minor


Report by xwhfcenter from github:
"There is a conflict in dependency of httpcore in module JDBC Driver"





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (KYLIN-2251) JDBC Driver httpcore dependency conflict

2016-12-06 Thread Billy Liu (JIRA)

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

Billy Liu commented on KYLIN-2251:
--

commit:
https://github.com/apache/kylin/commit/ea13af4d8aa6a5b25fc328ee1adaf2b454eddea0

> JDBC Driver httpcore dependency conflict
> 
>
> Key: KYLIN-2251
> URL: https://issues.apache.org/jira/browse/KYLIN-2251
> Project: Kylin
>  Issue Type: Bug
>  Components: Driver - JDBC
>Affects Versions: v1.6.0
>Reporter: Billy Liu
>Assignee: Billy Liu
>Priority: Minor
>
> Report by xwhfcenter from github:
> "There is a conflict in dependency of httpcore in module JDBC Driver"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (KYLIN-2251) JDBC Driver httpcore dependency conflict

2016-12-06 Thread Billy Liu (JIRA)

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

Billy Liu resolved KYLIN-2251.
--
   Resolution: Fixed
Fix Version/s: v1.6.1

> JDBC Driver httpcore dependency conflict
> 
>
> Key: KYLIN-2251
> URL: https://issues.apache.org/jira/browse/KYLIN-2251
> Project: Kylin
>  Issue Type: Bug
>  Components: Driver - JDBC
>Affects Versions: v1.6.0
>Reporter: Billy Liu
>Assignee: Billy Liu
>Priority: Minor
> Fix For: v1.6.1
>
>
> Report by xwhfcenter from github:
> "There is a conflict in dependency of httpcore in module JDBC Driver"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (KYLIN-2252) Enhance project/model/cube name check

2016-12-06 Thread Billy Liu (JIRA)
Billy Liu created KYLIN-2252:


 Summary: Enhance project/model/cube name check
 Key: KYLIN-2252
 URL: https://issues.apache.org/jira/browse/KYLIN-2252
 Project: Kylin
  Issue Type: Improvement
  Components: REST Service
Affects Versions: v1.6.0
Reporter: Billy Liu
Assignee: Billy Liu
Priority: Minor


Enhance the project/model/cube name check in Controller side, only letters, 
numbers and underline are valid. Others will throw out BadRequestException.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (KYLIN-2252) Enhance project/model/cube name check

2016-12-06 Thread Billy Liu (JIRA)

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

Billy Liu resolved KYLIN-2252.
--
   Resolution: Fixed
Fix Version/s: v1.6.1

commit id: 1e787165edee713a59db8627e70f79edabfd7d9d

> Enhance project/model/cube name check
> -
>
> Key: KYLIN-2252
> URL: https://issues.apache.org/jira/browse/KYLIN-2252
> Project: Kylin
>  Issue Type: Improvement
>  Components: REST Service
>Affects Versions: v1.6.0
>Reporter: Billy Liu
>Assignee: Billy Liu
>Priority: Minor
> Fix For: v1.6.1
>
>
> Enhance the project/model/cube name check in Controller side, only letters, 
> numbers and underline are valid. Others will throw out BadRequestException.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (KYLIN-1936) Improve enable limit logic (exactAggregation is too strict)

2016-12-06 Thread qstar (JIRA)

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

qstar commented on KYLIN-1936:
--

Hi,there
I use official release binary tar kylin 1.5.4, hbase 0.98.16, the cube(40GB+), 
when I send sql "select * table_name limit 5" like this, I couldn't get result 
from kylin, after a while it comes with error saying region is offline, this 
time hbase didn't crash but no results.I have followed kylin 
https://issues.apache.org/jira/browse/KYLIN-1787 and 
https://issues.apache.org/jira/browse/KYLIN-1792, but all won't resolve my 
problem, please help me work this out

> Improve enable limit logic (exactAggregation is too strict)
> ---
>
> Key: KYLIN-1936
> URL: https://issues.apache.org/jira/browse/KYLIN-1936
> Project: Kylin
>  Issue Type: Improvement
>Affects Versions: v1.5.3
>Reporter: hongbin ma
>Assignee: hongbin ma
> Fix For: v1.5.4
>
>
> from zhaotians...@meizu.com:
> recently I got the following error while execute query on a cube which is not 
> that big( about 400mb, 20milion record)
> ==
> Error while executing SQL "select FCRASHTIME,count(1) from 
> UXIP.EDL_FDT_OUC_UPLOAD_FILES group by FCRASH_ANALYSIS_ID,FCRASHTIME limit 
> 1": Scan row count exceeded threshold: 1000, please add filter condition 
> to narrow down backend scan range, like where clause.
> I guess what  it scan were the intermediate result, but It doesn't any order 
> by,also the result count is limit to just 1.so it could scan to find any 
> record with those two dimension and wala.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (KYLIN-2180) Add project config and make config priority become "cube > project > server"

2016-12-06 Thread kangkaisen (JIRA)

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

kangkaisen commented on KYLIN-2180:
---

Hi,[~liyang.g...@gmail.com],please review this patch when you have time.  Thank 
you.
The front-end code of this patch should be OK and has run a long time in our 
production env.

> Add project config and make config priority become "cube > project > server"
> 
>
> Key: KYLIN-2180
> URL: https://issues.apache.org/jira/browse/KYLIN-2180
> Project: Kylin
>  Issue Type: New Feature
>  Components: Metadata
>Affects Versions: v1.5.4.1
>Reporter: kangkaisen
>Assignee: kangkaisen
> Attachments: KYLIN-2180-tmp.patch, KYLIN-2180.patch
>
>
> There are cases we want to override global kylin.properties in the scope of a 
> project. E.g. the queue name of Hadoop job.
> Finally, the config priority for Kylin should be "cube > project > server". I 
> think which is reasonable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)