[jira] [Commented] (KYLIN-2085) PrepareStatement return incorrect result in some cases
[
https://issues.apache.org/jira/browse/KYLIN-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15570668#comment-15570668
]
Dong Li commented on KYLIN-2085:
Fixed in commit 8fbfc580c1b89e3e0065027eb22f8e3e5b7e0c67
> PrepareStatement return incorrect result in some cases
> --
>
> Key: KYLIN-2085
> URL: https://issues.apache.org/jira/browse/KYLIN-2085
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Reporter: Dong Li
>Assignee: Dong Li
> Fix For: v1.6.0
>
>
> With Kylin sample data,execute following SQL can get result:
> select count(*) from kylin_sales where lstg_format_name>='ABIN' and
> lstg_format_name<=''
> Result: 4054
> Send post with prestate:
> POST http://localhost:7070/kylin/api/query/prestate
> {"sql":"select count(*) from kylin_sales where lstg_format_name>=? and
> lstg_format_name<=?","offset":0,"limit":5,"acceptPartial":true,"project":"learn_kylin","params":[{"className":"java.lang.String",
> "value":"ABIN"},{"className":"java.lang.String", "value":""}]}
> Result: 0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KYLIN-1990) The SweetAlert at the front page may out of the page if the content is too long.
[ https://issues.apache.org/jira/browse/KYLIN-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15570660#comment-15570660 ] Zhong,Jason commented on KYLIN-1990: Hi [~liguohui], I have reviewed your patch. 400px max-height still cause button not visible issue on small screen. suggest small height 300px. And since SweetAlert is used everywhere in page, how about update this style to all SweetAlert. You can do this with small change, only add overflow and max-height to class ".sweet-alert.text-muted". > The SweetAlert at the front page may out of the page if the content is too > long. > > > Key: KYLIN-1990 > URL: https://issues.apache.org/jira/browse/KYLIN-1990 > Project: Kylin > Issue Type: Bug >Affects Versions: v1.5.3 >Reporter: Guohui LI >Assignee: Zhong,Jason > Fix For: v1.6.0 > > Attachments: KYLIN-1990.patch > > > At the front page, SweetAlert is used to point out some info. But if the > content of the Alert is too long, buttons in the bottom will not visible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KYLIN-2085) PrepareStatement return incorrect result in some cases
[
https://issues.apache.org/jira/browse/KYLIN-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dong Li resolved KYLIN-2085.
Resolution: Fixed
Fix Version/s: v1.6.0
> PrepareStatement return incorrect result in some cases
> --
>
> Key: KYLIN-2085
> URL: https://issues.apache.org/jira/browse/KYLIN-2085
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Reporter: Dong Li
>Assignee: Dong Li
> Fix For: v1.6.0
>
>
> With Kylin sample data,execute following SQL can get result:
> select count(*) from kylin_sales where lstg_format_name>='ABIN' and
> lstg_format_name<=''
> Result: 4054
> Send post with prestate:
> POST http://localhost:7070/kylin/api/query/prestate
> {"sql":"select count(*) from kylin_sales where lstg_format_name>=? and
> lstg_format_name<=?","offset":0,"limit":5,"acceptPartial":true,"project":"learn_kylin","params":[{"className":"java.lang.String",
> "value":"ABIN"},{"className":"java.lang.String", "value":""}]}
> Result: 0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KYLIN-2052) Edit "Top N" measure, the "group by" column wasn't displayed
[ https://issues.apache.org/jira/browse/KYLIN-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-2052: - Attachment: 0001-KYLIN-2052-the-group-by-column-wasn-t-displayed.patch I have fixed this bug.Please check it.Thanks. > Edit "Top N" measure, the "group by" column wasn't displayed > > > Key: KYLIN-2052 > URL: https://issues.apache.org/jira/browse/KYLIN-2052 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.5.4, v1.5.4.1 >Reporter: Shaofeng SHI >Assignee: Zhong,Jason >Priority: Minor > Attachments: > 0001-KYLIN-2052-the-group-by-column-wasn-t-displayed.patch, Screen Shot > 2016-09-26 at 2.12.52 PM.png, Screen Shot 2016-09-26 at 2.13.02 PM.png > > > When edit the "kylin_sales" cube, in the measure page, click "Edit" button on > the "Top Seller" measure, the "group by" column list is empty, "seller_id" > wasn't recognized well; If click "Save" directly, Kylin will report error. > See the screen shot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2092) Region server not fully used during cube building
Hubert Zhang created KYLIN-2092: --- Summary: Region server not fully used during cube building Key: KYLIN-2092 URL: https://issues.apache.org/jira/browse/KYLIN-2092 Project: Kylin Issue Type: Bug Reporter: Hubert Zhang During cube building process most of the time only two region servers are under heavily load while other region servers are idle. The two region servers which are busy keeps changing during the build. Buy there is always up to two region servers running busy. Wonder if there is something related to the key setup or configuration issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2091) Add API to init the start-point (of each parition) for streaming cube
Shaofeng SHI created KYLIN-2091: --- Summary: Add API to init the start-point (of each parition) for streaming cube Key: KYLIN-2091 URL: https://issues.apache.org/jira/browse/KYLIN-2091 Project: Kylin Issue Type: Improvement Components: REST Service, streaming Reporter: Shaofeng SHI Assignee: Shaofeng SHI Fix For: v1.6.0 Just like a normal cube need a "partition start date" on creation (which will be used as the start point of the first segment), a streaming cube also need a starting point of the topic; but it will be a collection of offsets (for all partitions). Otherwise Kylin has to build from the topic's very begining, which may not be expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2089) Make update HBase coprocessor concurrent
kangkaisen created KYLIN-2089: - Summary: Make update HBase coprocessor concurrent Key: KYLIN-2089 URL: https://issues.apache.org/jira/browse/KYLIN-2089 Project: Kylin Issue Type: Improvement Components: Tools, Build and Test Affects Versions: v1.5.4.1 Reporter: kangkaisen Assignee: kangkaisen When we have thousands of HBase tables and update the coprocessor, it will take several hours. Which means we must stop query service for hours, so we should make updating HBase coprocessor concurrent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2087) Support SSL or TLS encryption in sending email
[ https://issues.apache.org/jira/browse/KYLIN-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-2087: Assignee: (was: Dong Li) Fix Version/s: Backlog > Support SSL or TLS encryption in sending email > -- > > Key: KYLIN-2087 > URL: https://issues.apache.org/jira/browse/KYLIN-2087 > Project: Kylin > Issue Type: New Feature > Components: Job Engine >Reporter: Shaofeng SHI > Fix For: Backlog > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2087) Support SSL or TLS encryption in sending email
[ https://issues.apache.org/jira/browse/KYLIN-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-2087: Priority: Minor (was: Major) > Support SSL or TLS encryption in sending email > -- > > Key: KYLIN-2087 > URL: https://issues.apache.org/jira/browse/KYLIN-2087 > Project: Kylin > Issue Type: New Feature > Components: Job Engine >Reporter: Shaofeng SHI >Priority: Minor > Fix For: Backlog > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2087) Support SSL or TLS encryption in sending email
Shaofeng SHI created KYLIN-2087: --- Summary: Support SSL or TLS encryption in sending email Key: KYLIN-2087 URL: https://issues.apache.org/jira/browse/KYLIN-2087 Project: Kylin Issue Type: New Feature Components: Job Engine Reporter: Shaofeng SHI Assignee: Dong Li -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2086) Still report error when there is more than 12 dimensions in one agg group
[ https://issues.apache.org/jira/browse/KYLIN-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-2086: Description: There is duplicated login in CubeDesc.validate() and AggregationGroupRule; and in AggregationGroupRule it still check the dimension numbers with "kylin.cube.aggrgroup.max.size", which has been marked as deprecated. > Still report error when there is more than 12 dimensions in one agg group > - > > Key: KYLIN-2086 > URL: https://issues.apache.org/jira/browse/KYLIN-2086 > Project: Kylin > Issue Type: Bug > Components: Metadata >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI > Fix For: v1.6.0 > > > There is duplicated login in CubeDesc.validate() and AggregationGroupRule; > and in AggregationGroupRule it still check the dimension numbers with > "kylin.cube.aggrgroup.max.size", which has been marked as deprecated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
