[jira] [Comment Edited] (KYLIN-2286) global snapshot table for one cube
[ https://issues.apache.org/jira/browse/KYLIN-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15753713#comment-15753713 ] Shaofeng SHI edited comment on KYLIN-2286 at 12/16/16 7:34 AM: --- This sounds like the scenario of "Slowly Changing Dimensions", which isn't well supported today: If user wants get history cube be updated (after changing lookup table), he need go back to refresh those history segments. Yu, is there any pre-condition for using global snapshot? I think all dimension columns in lookuptable should be "drived", right? was (Author: shaofengshi): This sounds like the scenario of "Slowly Changing Dimensions", which isn't well supported today: If user wants get history cube be updated (after changing lookup table), he need go back to refresh those history segments. Yu, is there any prediction for using global snapshot? I think all dimension columns in lookuptable should be "drived", right? > global snapshot table for one cube > --- > > Key: KYLIN-2286 > URL: https://issues.apache.org/jira/browse/KYLIN-2286 > Project: Kylin > Issue Type: Improvement >Reporter: fengYu >Assignee: fengYu > > I current version, Kylin build a snapshot table for a segment and isolate > with each other in the same cube, even though some segments share the same > snapshot table storage . > I some scene， we need global snapshot table for one cube, such as we has a > cube with snapshot table,ID is PK，the first day, the table look like: > id name > 1 A > 2 B > 3 C > the query 'select name, count(1) from fact join dimension group by name' get > result: > A xx > B xx > C xx > the next day(segment), lookup table modified, it looks like : > id name > 1 A > 2 D > 3 E > the same query return : > A xx > B xx > C xx > D xx > E xx > However B and D, C and E has the same ID, we need the newest result. so a > global snapshot table shared by all segments which has always the newest > values is needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2286) global snapshot table for one cube
[ https://issues.apache.org/jira/browse/KYLIN-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15753713#comment-15753713 ] Shaofeng SHI commented on KYLIN-2286: - This sounds like the scenario of "Slowly Changing Dimensions", which isn't well supported today: If user wants get history cube be updated (after changing lookup table), he need go back to refresh those history segments. Yu, is there any prediction for using global snapshot? I think all dimension columns in lookuptable should be "drived", right? > global snapshot table for one cube > --- > > Key: KYLIN-2286 > URL: https://issues.apache.org/jira/browse/KYLIN-2286 > Project: Kylin > Issue Type: Improvement >Reporter: fengYu >Assignee: fengYu > > I current version, Kylin build a snapshot table for a segment and isolate > with each other in the same cube, even though some segments share the same > snapshot table storage . > I some scene， we need global snapshot table for one cube, such as we has a > cube with snapshot table,ID is PK，the first day, the table look like: > id name > 1 A > 2 B > 3 C > the query 'select name, count(1) from fact join dimension group by name' get > result: > A xx > B xx > C xx > the next day(segment), lookup table modified, it looks like : > id name > 1 A > 2 D > 3 E > the same query return : > A xx > B xx > C xx > D xx > E xx > However B and D, C and E has the same ID, we need the newest result. so a > global snapshot table shared by all segments which has always the newest > values is needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2288) Kylin treat empty string as error measure which is inconsistent with hive
[ https://issues.apache.org/jira/browse/KYLIN-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuanlei Ni updated KYLIN-2288: --- Fix Version/s: Future > Kylin treat empty string as error measure which is inconsistent with hive > - > > Key: KYLIN-2288 > URL: https://issues.apache.org/jira/browse/KYLIN-2288 > Project: Kylin > Issue Type: Bug > Components: Metadata >Affects Versions: all >Reporter: Chuanlei Ni >Assignee: Shaofeng SHI > Fix For: Future > > > Assume we have a hive table > name, age > tom, 10 > jack, (empty string) > if we execute > select count(age) from thistable; > we can get 10 as the result. (my hive version is 0.13.1) > But Kylin can build cube for this case as > BigDecimalIngester/DoubleIngester/LongIngester cannot recongnize empty string -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2288) Kylin treat empty string as error measure which is inconsistent with hive
[ https://issues.apache.org/jira/browse/KYLIN-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuanlei Ni updated KYLIN-2288: --- Description: Assume we have a hive table name, age tom, 10 jack, (empty string) if we execute select count(age) from thistable; we can get 10 as the result. (my hive version is 0.13.1) But Kylin can not build cube for this case as BigDecimalIngester/DoubleIngester/LongIngester cannot recongnize empty string was: Assume we have a hive table name, age tom, 10 jack, (empty string) if we execute select count(age) from thistable; we can get 10 as the result. (my hive version is 0.13.1) But Kylin can build cube for this case as BigDecimalIngester/DoubleIngester/LongIngester cannot recongnize empty string > Kylin treat empty string as error measure which is inconsistent with hive > - > > Key: KYLIN-2288 > URL: https://issues.apache.org/jira/browse/KYLIN-2288 > Project: Kylin > Issue Type: Bug > Components: Metadata >Affects Versions: all >Reporter: Chuanlei Ni >Assignee: Shaofeng SHI > Fix For: Future > > > Assume we have a hive table > name, age > tom, 10 > jack, (empty string) > if we execute > select count(age) from thistable; > we can get 10 as the result. (my hive version is 0.13.1) > But Kylin can not build cube for this case as > BigDecimalIngester/DoubleIngester/LongIngester cannot recongnize empty string -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2288) Kylin treat empty string as error measure which is inconsistent with hive
Chuanlei Ni created KYLIN-2288: -- Summary: Kylin treat empty string as error measure which is inconsistent with hive Key: KYLIN-2288 URL: https://issues.apache.org/jira/browse/KYLIN-2288 Project: Kylin Issue Type: Bug Components: Metadata Affects Versions: all Reporter: Chuanlei Ni Assignee: Shaofeng SHI Assume we have a hive table name, age tom, 10 jack, (empty string) if we execute select count(age) from thistable; we can get 10 as the result. (my hive version is 0.13.1) But Kylin can build cube for this case as BigDecimalIngester/DoubleIngester/LongIngester cannot recongnize empty string -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2289) Redo SSB Bemchmark Test
XIE FAN created KYLIN-2289: -- Summary: Redo SSB Bemchmark Test Key: KYLIN-2289 URL: https://issues.apache.org/jira/browse/KYLIN-2289 Project: Kylin Issue Type: Test Environment: UCloud cluster. 4 nodes, 32 cup,100G memory for each node. Reporter: XIE FAN Assignee: XIE FAN Redo the ssb benchmark test on our own cluster and compare the performance of Kylin1.6、Hive and Spark Sql. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-232) Support multi-tenant architecture
[ https://issues.apache.org/jira/browse/KYLIN-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15753637#comment-15753637 ] Shaofeng SHI commented on KYLIN-232: Hi Mathias, HBase namespace support hasn't been implemented; welcome to dev and then contribute back; To implement it, firstly adding a new parameter for namespace in KylinConfigBase.java, then modifying the CreateHTableJob.java to using this namespace when creating the table. Other places which operates the HTables may also need be updated, like "StorageCleanupJob", etc. Besides, it need test cases to cover with and without namespace enabled. > Support multi-tenant architecture > - > > Key: KYLIN-232 > URL: https://issues.apache.org/jira/browse/KYLIN-232 > Project: Kylin > Issue Type: Wish > Components: General >Reporter: Luke Han >Assignee: Luke Han > Labels: github-import > Fix For: Backlog > > > Support multi-tenant for large scale deployment. > Reference: http://en.wikipedia.org/wiki/Multitenancy > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/273 > Created by: [lukehan|https://github.com/lukehan] > Labels: > Milestone: Backlog > Created at: Fri Dec 26 13:31:37 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2287) Speed up model and cube list load in Web
kangkaisen created KYLIN-2287: - Summary: Speed up model and cube list load in Web Key: KYLIN-2287 URL: https://issues.apache.org/jira/browse/KYLIN-2287 Project: Kylin Issue Type: Improvement Components: Web Affects Versions: v1.6.0 Reporter: kangkaisen Assignee: kangkaisen Priority: Critical Currently, if a project has more than one hundred cubes and models, the "Model" page load will take a long time because there are a lot of http requests. So we need to reduce and defer the http requests when initially load "Model" page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2286) global snapshot table for one cube
fengYu created KYLIN-2286: - Summary: global snapshot table for one cube Key: KYLIN-2286 URL: https://issues.apache.org/jira/browse/KYLIN-2286 Project: Kylin Issue Type: Improvement Reporter: fengYu Assignee: fengYu I current version, Kylin build a snapshot table for a segment and isolate with each other in the same cube, even though some segments share the same snapshot table storage . I some scene， we need global snapshot table for one cube, such as we has a cube with snapshot table,ID is PK，the first day, the table look like: id name 1 A 2 B 3 C the query 'select name, count(1) from fact join dimension group by name' get result: A xx B xx C xx the next day(segment), lookup table modified, it looks like : id name 1 A 2 D 3 E the same query return : A xx B xx C xx D xx E xx However B and D, C and E has the same ID, we need the newest result. so a global snapshot table shared by all segments which has always the newest values is needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2267) When FK/PK column type mismatched, get error on query: "NullPointerException: Column ### does not exist in row key desc"
[
https://issues.apache.org/jira/browse/KYLIN-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liyang updated KYLIN-2267:
--
Labels: newbie (was: )
> When FK/PK column type mismatched, get error on query: "NullPointerException:
> Column ### does not exist in row key desc"
>
>
> Key: KYLIN-2267
> URL: https://issues.apache.org/jira/browse/KYLIN-2267
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Reporter: Shaofeng SHI
>Priority: Minor
> Labels: newbie
>
> I got this error in a cube which has one fact table and one lookup table; All
> dimensions are normal, which looks be a very simple case (and the FK column
> does exist on rowkey descriptor), but I got this error on every query that
> uses columns on the lookup table; The error log is as below:
> {code}
> 2016-12-08 13:58:25,177 INFO [http-bio-7070-exec-5] routing.QueryRouter:72 :
> The realizations remaining: [his_realtime_cube_v7(CUBE)] And the final chosen
> one is the first one
> 2016-12-08 13:58:25,219 DEBUG [http-bio-7070-exec-5]
> enumerator.OLAPEnumerator:100 : query storage...
> 2016-12-08 13:58:25,220 ERROR [http-bio-7070-exec-5]
> controller.QueryController:208 : Exception when execute sql
> java.sql.SQLException: Error while executing SQL "select count(*) as "m0"
> from "DEFAULT"."HIS_REALTIME" as "HIS_REALTIME" join
> "DEFAULT"."V_STKCODE_INDUSTRYINFO2" as "V_STKCODE_INDUSTRYINFO2" on
> "HIS_REALTIME"."STOCK_CODE" = "V_STKCODE_INDUSTRYINFO2"."STK_CODE"
> LIMIT 5": Column DEFAULT.V_STKCODE_INDUSTRYINFO2.STK_CODE does not exist
> in row key desc
> at org.apache.calcite.avatica.Helper.createException(Helper.java:56)
> at org.apache.calcite.avatica.Helper.createException(Helper.java:41)
> at
> org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:147)
> at
> org.apache.calcite.avatica.AvaticaStatement.executeQuery(AvaticaStatement.java:208)
> at
> org.apache.kylin.rest.service.QueryService.execute(QueryService.java:407)
> at
> org.apache.kylin.rest.service.QueryService.queryWithSqlMassage(QueryService.java:321)
> at
> org.apache.kylin.rest.service.QueryService.query(QueryService.java:128)
> at
> org.apache.kylin.rest.controller.QueryController.doQueryWithCache(QueryController.java:191)
> at
> org.apache.kylin.rest.controller.QueryController.query(QueryController.java:94)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:221)
> at
> org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:136)
> at
> org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:104)
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandleMethod(RequestMappingHandlerAdapter.java:743)
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:672)
> at
> org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:82)
> at
> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:933)
> at
> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:867)
> at
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:951)
> at
> org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:853)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:650)
> at
> org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:827)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at
>
[jira] [Commented] (KYLIN-2267) When FK/PK column type mismatched, get error on query: "NullPointerException: Column ### does not exist in row key desc"
[
https://issues.apache.org/jira/browse/KYLIN-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15753512#comment-15753512
]
liyang commented on KYLIN-2267:
---
Somehow I believe this was fixed. Need to verify again on latest code.
> When FK/PK column type mismatched, get error on query: "NullPointerException:
> Column ### does not exist in row key desc"
>
>
> Key: KYLIN-2267
> URL: https://issues.apache.org/jira/browse/KYLIN-2267
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Reporter: Shaofeng SHI
>Priority: Minor
>
> I got this error in a cube which has one fact table and one lookup table; All
> dimensions are normal, which looks be a very simple case (and the FK column
> does exist on rowkey descriptor), but I got this error on every query that
> uses columns on the lookup table; The error log is as below:
> {code}
> 2016-12-08 13:58:25,177 INFO [http-bio-7070-exec-5] routing.QueryRouter:72 :
> The realizations remaining: [his_realtime_cube_v7(CUBE)] And the final chosen
> one is the first one
> 2016-12-08 13:58:25,219 DEBUG [http-bio-7070-exec-5]
> enumerator.OLAPEnumerator:100 : query storage...
> 2016-12-08 13:58:25,220 ERROR [http-bio-7070-exec-5]
> controller.QueryController:208 : Exception when execute sql
> java.sql.SQLException: Error while executing SQL "select count(*) as "m0"
> from "DEFAULT"."HIS_REALTIME" as "HIS_REALTIME" join
> "DEFAULT"."V_STKCODE_INDUSTRYINFO2" as "V_STKCODE_INDUSTRYINFO2" on
> "HIS_REALTIME"."STOCK_CODE" = "V_STKCODE_INDUSTRYINFO2"."STK_CODE"
> LIMIT 5": Column DEFAULT.V_STKCODE_INDUSTRYINFO2.STK_CODE does not exist
> in row key desc
> at org.apache.calcite.avatica.Helper.createException(Helper.java:56)
> at org.apache.calcite.avatica.Helper.createException(Helper.java:41)
> at
> org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:147)
> at
> org.apache.calcite.avatica.AvaticaStatement.executeQuery(AvaticaStatement.java:208)
> at
> org.apache.kylin.rest.service.QueryService.execute(QueryService.java:407)
> at
> org.apache.kylin.rest.service.QueryService.queryWithSqlMassage(QueryService.java:321)
> at
> org.apache.kylin.rest.service.QueryService.query(QueryService.java:128)
> at
> org.apache.kylin.rest.controller.QueryController.doQueryWithCache(QueryController.java:191)
> at
> org.apache.kylin.rest.controller.QueryController.query(QueryController.java:94)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:221)
> at
> org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:136)
> at
> org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:104)
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandleMethod(RequestMappingHandlerAdapter.java:743)
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:672)
> at
> org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:82)
> at
> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:933)
> at
> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:867)
> at
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:951)
> at
> org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:853)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:650)
> at
> org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:827)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at
>
[jira] [Resolved] (KYLIN-1855) Inner-join query partially matches inner-join model can return incorrect result
[ https://issues.apache.org/jira/browse/KYLIN-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyang resolved KYLIN-1855. --- Resolution: Fixed > Inner-join query partially matches inner-join model can return incorrect > result > --- > > Key: KYLIN-1855 > URL: https://issues.apache.org/jira/browse/KYLIN-1855 > Project: Kylin > Issue Type: Improvement >Reporter: Zhong Yanghong >Assignee: liyang > Fix For: v1.5.4 > > Attachments: exclude_unused_joins.patch > > > A cube is based on a model in which a star schema is defined. In some cases, > the cube utilizes only a few lookup tables rather than all. In this case, > when creating the sql for the flat table, those lookup tables should not be > included. Otherwise, it will confuse users when query. If users do query > according to the definition of the flat table, error of no realization will > occur due to lack of the related join. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1855) Inner-join query partially matches inner-join model can return incorrect result
[ https://issues.apache.org/jira/browse/KYLIN-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15753420#comment-15753420 ] liyang commented on KYLIN-1855: --- Let me close this one, and see if similar concerns rise again. > Inner-join query partially matches inner-join model can return incorrect > result > --- > > Key: KYLIN-1855 > URL: https://issues.apache.org/jira/browse/KYLIN-1855 > Project: Kylin > Issue Type: Improvement >Reporter: Zhong Yanghong >Assignee: liyang > Fix For: v1.5.4 > > Attachments: exclude_unused_joins.patch > > > A cube is based on a model in which a star schema is defined. In some cases, > the cube utilizes only a few lookup tables rather than all. In this case, > when creating the sql for the flat table, those lookup tables should not be > included. Otherwise, it will confuse users when query. If users do query > according to the definition of the flat table, error of no realization will > occur due to lack of the related join. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2253) sql union did not remove duplicated records (distinct)
[ https://issues.apache.org/jira/browse/KYLIN-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15753311#comment-15753311 ] liyang commented on KYLIN-2253: --- Em.. we shall upgrade calcite again sometime. Any recommended version any body know? > sql union did not remove duplicated records (distinct) > --- > > Key: KYLIN-2253 > URL: https://issues.apache.org/jira/browse/KYLIN-2253 > Project: Kylin > Issue Type: Bug > Components: Driver - JDBC >Affects Versions: v1.5.4.1 > Environment: apache-kylin-1.6.0-hbase1.x-bin.tar.gz >Reporter: zhou degao >Priority: Critical > > sql like following: > select "LOOKUP_TIME_BY_DAY"."THE_YEAR" as "c0", > "LOOKUP_TIME_BY_DAY"."MONTH_OF_YEAR" as "c1" from "VCGBI_FACT_SALE" as > "VCGBI_FACT_SALE" join "LOOKUP_TIME_BY_DAY" as "LOOKUP_TIME_BY_DAY" on > "VCGBI_FACT_SALE"."DEAL_TIME" = "LOOKUP_TIME_BY_DAY"."THE_DATE" group by > "LOOKUP_TIME_BY_DAY"."THE_YEAR", "LOOKUP_TIME_BY_DAY"."MONTH_OF_YEAR" > union > select "LOOKUP_TIME_BY_DAY"."THE_YEAR" as "c0", > "LOOKUP_TIME_BY_DAY"."MONTH_OF_YEAR" as "c1" from > "VCGBI_FACT_PERSON_MISC_DATA" as "VCGBI_FACT_PERSON_MISC_DATA" join > "LOOKUP_TIME_BY_DAY" as "LOOKUP_TIME_BY_DAY" on > "VCGBI_FACT_PERSON_MISC_DATA"."TIME" = "LOOKUP_TIME_BY_DAY"."THE_DATE" group > by "LOOKUP_TIME_BY_DAY"."THE_YEAR", "LOOKUP_TIME_BY_DAY"."MONTH_OF_YEAR" > order by 1 ASC, 2 ASC > I got result like following: > 2016 1 > 2016 1 > 2016 2 > 2016 2 > 2016 3 > 2016 3 > 2016 4 > 2016 4 > 2016 5 > 2016 5 > 2016 6 > 2016 6 > 2016 7 > 2016 7 > 2016 8 > 2016 8 > 2016 9 > 2016 9 > 2016 10 > 2016 11 > 2016 12 -- 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"
[ https://issues.apache.org/jira/browse/KYLIN-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15753308#comment-15753308 ] liyang commented on KYLIN-2180: --- Thanks Kaisen!! The refactor patch is very good. Merged to master. :-) > 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 > Fix For: v1.6.1 > > Attachments: KYLIN-2180-refactor-ProjectRequest.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)
[jira] [Updated] (KYLIN-2180) Add project config and make config priority become "cube > project > server"
[ https://issues.apache.org/jira/browse/KYLIN-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyang updated KYLIN-2180: -- Attachment: (was: KYLIN-2180-tmp.patch) > 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 > Fix For: v1.6.1 > > Attachments: KYLIN-2180-refactor-ProjectRequest.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)
[jira] [Commented] (KYLIN-2006) Make job engine distributed and HA
[ https://issues.apache.org/jira/browse/KYLIN-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15753205#comment-15753205 ] liyang commented on KYLIN-2006: --- Document merged. > Make job engine distributed and HA > -- > > Key: KYLIN-2006 > URL: https://issues.apache.org/jira/browse/KYLIN-2006 > Project: Kylin > Issue Type: New Feature > Components: Job Engine >Reporter: kangkaisen >Assignee: kangkaisen > Fix For: v1.6.1 > > Attachments: KYLIN-2006-doc.patch, KYLIN-2006.patch > > > Currently, the Kylin job build server is single-point。 > In order to make Kylin job build server more extensible, available and > reliable, we should support distributed job build server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (KYLIN-2285) ffdfds
[ https://issues.apache.org/jira/browse/KYLIN-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billy Liu closed KYLIN-2285. Resolution: Invalid > ffdfds > -- > > Key: KYLIN-2285 > URL: https://issues.apache.org/jira/browse/KYLIN-2285 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: paldheeru39 >Assignee: Zhong,Jason > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2285) ffdfds
[ https://issues.apache.org/jira/browse/KYLIN-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15751976#comment-15751976 ] paldheeru39 commented on KYLIN-2285: gfdgfd > ffdfds > -- > > Key: KYLIN-2285 > URL: https://issues.apache.org/jira/browse/KYLIN-2285 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: paldheeru39 >Assignee: Zhong,Jason > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2285) ffdfds
paldheeru39 created KYLIN-2285: -- Summary: ffdfds Key: KYLIN-2285 URL: https://issues.apache.org/jira/browse/KYLIN-2285 Project: Kylin Issue Type: Bug Components: Web Reporter: paldheeru39 Assignee: Zhong,Jason -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2284) intersect_count function error
[ https://issues.apache.org/jira/browse/KYLIN-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luyuan Zhai updated KYLIN-2284: --- Attachment: intersect_count.correct result.png The result returned correct image > intersect_count function error > -- > > Key: KYLIN-2284 > URL: https://issues.apache.org/jira/browse/KYLIN-2284 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v1.6.0 > Environment: windows >Reporter: Luyuan Zhai >Assignee: liyang >Priority: Minor > Attachments: intersect_count.correct result.png, > intersect_count.error result.png > > > I explored on the Kylin Web GUI, using datasource learn_kylin, when I inputed > sql query"select intersect_count(seller_id, LSTG_FORMAT_NAME, > array['Others']) from KYLIN_SALES", it led to an error"Error while executing > SQL "select intersect_count(seller_id, LSTG_FORMAT_NAME, array['Others']) > from KYLIN_SALES LIMIT 5": Index: 1, Size: 1". > Yet when I inputed similar sql query including intersect_count function as > well, then it worked well and the result returned correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2284) intersect_count function error
[ https://issues.apache.org/jira/browse/KYLIN-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luyuan Zhai updated KYLIN-2284: --- Attachment: intersect_count.error result.png result error report > intersect_count function error > -- > > Key: KYLIN-2284 > URL: https://issues.apache.org/jira/browse/KYLIN-2284 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v1.6.0 > Environment: windows >Reporter: Luyuan Zhai >Assignee: liyang >Priority: Minor > Attachments: intersect_count.correct result.png, > intersect_count.error result.png > > > I explored on the Kylin Web GUI, using datasource learn_kylin, when I inputed > sql query"select intersect_count(seller_id, LSTG_FORMAT_NAME, > array['Others']) from KYLIN_SALES", it led to an error"Error while executing > SQL "select intersect_count(seller_id, LSTG_FORMAT_NAME, array['Others']) > from KYLIN_SALES LIMIT 5": Index: 1, Size: 1". > Yet when I inputed similar sql query including intersect_count function as > well, then it worked well and the result returned correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2284) intersect_count function error
Luyuan Zhai created KYLIN-2284: -- Summary: intersect_count function error Key: KYLIN-2284 URL: https://issues.apache.org/jira/browse/KYLIN-2284 Project: Kylin Issue Type: Bug Components: Query Engine Affects Versions: v1.6.0 Environment: windows Reporter: Luyuan Zhai Assignee: liyang Priority: Minor I explored on the Kylin Web GUI, using datasource learn_kylin, when I inputed sql query"select intersect_count(seller_id, LSTG_FORMAT_NAME, array['Others']) from KYLIN_SALES", it led to an error"Error while executing SQL "select intersect_count(seller_id, LSTG_FORMAT_NAME, array['Others']) from KYLIN_SALES LIMIT 5": Index: 1, Size: 1". Yet when I inputed similar sql query including intersect_count function as well, then it worked well and the result returned correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
