[jira] [Commented] (KYLIN-2483) SortedIteratorMergerWithLimit could be slower when number of total merge rows is small

2017-03-05 Thread hongbin ma (JIRA)

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

hongbin ma commented on KYLIN-2483:
---

just gave it another thought, disabling SortedIteratorMergerWithLimit with 
limit push down enabled will return wrong results. Since it's always   tempting 
to enable limit push down, we'll have to suffer the cost of 
SortedIteratorMergerWithLimit.

> SortedIteratorMergerWithLimit could be slower when number of total merge rows 
> is small
> --
>
> Key: KYLIN-2483
> URL: https://issues.apache.org/jira/browse/KYLIN-2483
> Project: Kylin
>  Issue Type: Improvement
>Reporter: hongbin ma
>Assignee: hongbin ma
>
> if the pushed down limit is small enough (say less than 100), 
> SortedIteratorMergerWithLimit will bring RELATIVELY significant costs. I'm 
> adding a new configuration entry called 
> kylin.query.merge-sort-partition-results.min-limit (default 100) to fix this 
> issue



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Closed] (KYLIN-2483) SortedIteratorMergerWithLimit could be slower when number of total merge rows is small

2017-03-05 Thread hongbin ma (JIRA)

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

hongbin ma closed KYLIN-2483.
-
Resolution: Not A Problem

> SortedIteratorMergerWithLimit could be slower when number of total merge rows 
> is small
> --
>
> Key: KYLIN-2483
> URL: https://issues.apache.org/jira/browse/KYLIN-2483
> Project: Kylin
>  Issue Type: Improvement
>Reporter: hongbin ma
>Assignee: hongbin ma
>
> if the pushed down limit is small enough (say less than 100), 
> SortedIteratorMergerWithLimit will bring RELATIVELY significant costs. I'm 
> adding a new configuration entry called 
> kylin.query.merge-sort-partition-results.min-limit (default 100) to fix this 
> issue



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (KYLIN-2485) Test thread safety of HDFSResourceStore

2017-03-05 Thread XIE FAN (JIRA)
XIE FAN created KYLIN-2485:
--

 Summary: Test thread safety of HDFSResourceStore
 Key: KYLIN-2485
 URL: https://issues.apache.org/jira/browse/KYLIN-2485
 Project: Kylin
  Issue Type: Sub-task
Reporter: XIE FAN
Assignee: XIE FAN






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (KYLIN-2484) Kylin spark engine doesn't support source from Kafka

2017-03-05 Thread Shaofeng SHI (JIRA)

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

Shaofeng SHI updated KYLIN-2484:

Description: 
The current spark engine uses Spark's HiveConext to read data, so it required 
that the source is in Hive; this means the Streaming cube couldn't be built 
with Spark engine.

So far will add a validation with a meaningful message when user uses this 
combination. Later Kylin need provide solution for this.

  was:
The current spark engine uses Spark's HiveConext to read data, so it required 
that the source is in Hive; this means the Streaming cube couldn't be built 
with Spark engine.



> Kylin spark engine doesn't support source from Kafka
> 
>
> Key: KYLIN-2484
> URL: https://issues.apache.org/jira/browse/KYLIN-2484
> Project: Kylin
>  Issue Type: Bug
>  Components: Spark Engine
>Affects Versions: v2.0.0
>Reporter: Shaofeng SHI
> Fix For: Backlog
>
>
> The current spark engine uses Spark's HiveConext to read data, so it required 
> that the source is in Hive; this means the Streaming cube couldn't be built 
> with Spark engine.
> So far will add a validation with a meaningful message when user uses this 
> combination. Later Kylin need provide solution for this.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (KYLIN-2484) Kylin spark engine doesn't support source from Kafka

2017-03-05 Thread Shaofeng SHI (JIRA)
Shaofeng SHI created KYLIN-2484:
---

 Summary: Kylin spark engine doesn't support source from Kafka
 Key: KYLIN-2484
 URL: https://issues.apache.org/jira/browse/KYLIN-2484
 Project: Kylin
  Issue Type: Bug
  Components: Spark Engine
Affects Versions: v2.0.0
Reporter: Shaofeng SHI
 Fix For: Backlog


The current spark engine uses Spark's HiveConext to read data, so it required 
that the source is in Hive; this means the Streaming cube couldn't be built 
with Spark engine.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Closed] (KYLIN-2475) DESCBROKEN Cube cannot be disabled

2017-03-05 Thread Luyuan Zhai (JIRA)

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

Luyuan Zhai closed KYLIN-2475.
--
Resolution: Not A Bug

Kylin doesn't have this issue. Do apologize for mis-open this one.

> DESCBROKEN Cube cannot be disabled
> --
>
> Key: KYLIN-2475
> URL: https://issues.apache.org/jira/browse/KYLIN-2475
> Project: Kylin
>  Issue Type: Bug
>Affects Versions: all
> Environment: CDH5.7 
>Reporter: Luyuan Zhai
> Attachments: 图片1.png
>
>
> A ready Cube's metadata is changed and it turns to be DESCBROKEN.
> Then it cannot be disabled, thus being totally unreasonable.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (KYLIN-2483) SortedIteratorMergerWithLimit could be slower when number of total merge rows is small

2017-03-05 Thread hongbin ma (JIRA)
hongbin ma created KYLIN-2483:
-

 Summary: SortedIteratorMergerWithLimit could be slower when number 
of total merge rows is small
 Key: KYLIN-2483
 URL: https://issues.apache.org/jira/browse/KYLIN-2483
 Project: Kylin
  Issue Type: Improvement
Reporter: hongbin ma
Assignee: hongbin ma


if the pushed down limit is small enough (say less than 100), 
SortedIteratorMergerWithLimit will bring RELATIVELY significant costs. I'm 
adding a new configuration entry called 
kylin.query.merge-sort-partition-results.min-limit (default 100) to fix this 
issue



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (KYLIN-2482) build a streaming cube, I meet a 404 error

2017-03-05 Thread Shaofeng SHI (JIRA)

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

Shaofeng SHI commented on KYLIN-2482:
-

I made a change before 2.0 beta; the origin purpose is to remove an outdata tip 
"Streaming cube build is not supported on UI", but seems it is still referenced 
in other places: 
https://github.com/apache/kylin/commit/cdfde7cb1ecb583af56dfb2f1255f819b1d93131



> build a streaming cube, I meet a 404 error
> --
>
> Key: KYLIN-2482
> URL: https://issues.apache.org/jira/browse/KYLIN-2482
> Project: Kylin
>  Issue Type: Bug
>Affects Versions: v2.0.0
>Reporter: liyang
>
> Reported by mqb <1511013...@qq.com>:
>  When I using kylin-2.0.0-beta web interface to build a streaming cube, I 
> meet a 404 error. Does anyone meet the same problem? The  messages of chorme 
> browser's console is as follows:
>   http://*.*.*.*:7070/kylin/streamingBuild.html 404 (OK)
>   7da2a5dd-81c9-4395-8972-61cb2e91010a200xhr
> scripts.min.20170224095843.js:8660245 B
>   SSCube1200xhrscripts.min.20170224095843.js:86601.0 KB
>   DEFAULT.TEST200xhrscripts.min.20170224095843.js:86601.2 KB
>   streamingBuild.html404xhr   scripts.min.20170224095843.js:8660
> 1.4 KB



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)