[jira] [Commented] (KYLIN-3107) An alert dialog will pop up warning "Failed to load bar chat" when the user enter or log out from the "Dashboard" page.
[ https://issues.apache.org/jira/browse/KYLIN-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951691#comment-16951691 ] luguosheng commented on KYLIN-3107: --- Before Dashboard well worked you should build system cube first . [toturial|http://kylin.apache.org/cn/docs/tutorial/use_dashboard.html] > An alert dialog will pop up warning "Failed to load bar chat" when the user > enter or log out from the "Dashboard" page. > --- > > Key: KYLIN-3107 > URL: https://issues.apache.org/jira/browse/KYLIN-3107 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.3.0 >Reporter: peng.jianhua >Assignee: luguosheng >Priority: Minor > Attachments: alert_dialog_pop_up_when_enter_Dashboard_page.PNG, > alert_dialog_pop_up_when_log_out_from_Dashboard_page.PNG > > > An alert dialog will pop up warning "Failed to load bar chat" when the user > enter or log out from the "Dashboard" page. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (KYLIN-3107) An alert dialog will pop up warning "Failed to load bar chat" when the user enter or log out from the "Dashboard" page.
[ https://issues.apache.org/jira/browse/KYLIN-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng reassigned KYLIN-3107: - Assignee: luguosheng (was: peng.jianhua) > An alert dialog will pop up warning "Failed to load bar chat" when the user > enter or log out from the "Dashboard" page. > --- > > Key: KYLIN-3107 > URL: https://issues.apache.org/jira/browse/KYLIN-3107 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.3.0 >Reporter: peng.jianhua >Assignee: luguosheng >Priority: Minor > Attachments: alert_dialog_pop_up_when_enter_Dashboard_page.PNG, > alert_dialog_pop_up_when_log_out_from_Dashboard_page.PNG > > > An alert dialog will pop up warning "Failed to load bar chat" when the user > enter or log out from the "Dashboard" page. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (KYLIN-3212) Replace "array[]" with "array()" when pushing down query to Hive
[ https://issues.apache.org/jira/browse/KYLIN-3212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng reassigned KYLIN-3212: - Assignee: luguosheng (was: liyang) > Replace "array[]" with "array()" when pushing down query to Hive > > > Key: KYLIN-3212 > URL: https://issues.apache.org/jira/browse/KYLIN-3212 > Project: Kylin > Issue Type: New Feature > Components: Query Engine >Reporter: Chuqian Yu >Assignee: luguosheng >Priority: Minor > > Hi , Kylin community. > I am using "intersect_count" to calculate the conversion rate and want to > pushing it down to hive when no cube can answer. But the array format > "array[]" is not readable in hive .So I need to add a method in > org.apache.kylin.source.adhocquery.HivePushDownConverter in order to replace > "array[]" to "array()" when pushing down query to Hive. > Any suggestions? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (KYLIN-1648) Show Kylin Build Version on UI
[ https://issues.apache.org/jira/browse/KYLIN-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng reassigned KYLIN-1648: - Assignee: luguosheng (was: Jason Zhong) > Show Kylin Build Version on UI > -- > > Key: KYLIN-1648 > URL: https://issues.apache.org/jira/browse/KYLIN-1648 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: all >Reporter: Richard Calaba >Assignee: luguosheng >Priority: Minor > Labels: newbie > > For people who are testing various releases of Kylin - it would be very > beneficial if Web UI can show current Buiuld version. I.e. in the System > section where other config attributes are shown ... or on every page footer > section ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (KYLIN-1850) Show Kylin Version on GUI
[ https://issues.apache.org/jira/browse/KYLIN-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng reassigned KYLIN-1850: - Assignee: luguosheng (was: Jason Zhong) > Show Kylin Version on GUI > - > > Key: KYLIN-1850 > URL: https://issues.apache.org/jira/browse/KYLIN-1850 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v1.5.2 >Reporter: qianqiaoneng >Assignee: luguosheng >Priority: Trivial > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (KYLIN-1024) UPPER not support in Kylin
[
https://issues.apache.org/jira/browse/KYLIN-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
luguosheng reassigned KYLIN-1024:
-
Assignee: luguosheng (was: liyang)
> UPPER not support in Kylin
> --
>
> Key: KYLIN-1024
> URL: https://issues.apache.org/jira/browse/KYLIN-1024
> Project: Kylin
> Issue Type: Sub-task
> Components: Query Engine
>Affects Versions: v0.7.1, v0.7.2, v1.0
>Reporter: Huang Hua
>Assignee: luguosheng
>Priority: Minor
>
> UPPER function doesn't work in WHERE clause,
> "org.apache.kylin.rest.exception.InternalErrorException: UPPER while
> executing SQL":
> select "MONDRIAN_REGION"."REGION_PROVINCE" as "c0",
> "MONDRIAN_REGION"."REGION_COUNTRY" as "c1"
> from "MONDRIAN_REGION" as "MONDRIAN_REGION"
> where ("MONDRIAN_REGION"."REGION_COUNTRY" = '??') and
> UPPER("MONDRIAN_REGION"."REGION_PROVINCE") = UPPER('??')
> group by "MONDRIAN_REGION"."REGION_PROVINCE",
> "MONDRIAN_REGION"."REGION_COUNTRY"
> order by CASE WHEN "MONDRIAN_REGION"."REGION_PROVINCE" IS NULL THEN 0 ELSE 1
> END, "MONDRIAN_REGION"."REGION_PROVINCE" ASC
> LIMIT 5
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KYLIN-4174) job statistics info is incorrect
[
https://issues.apache.org/jira/browse/KYLIN-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939144#comment-16939144
]
luguosheng commented on KYLIN-4174:
---
It was fixed. linked to jira number:KYLIN-4100 and code in
https://github.com/apache/kylin/pull/857
but when you full refresh page it will always double request overview api when
project change from null to a certain value because of the project notice
event. if you just change menu to this page. it will work well.
> job statistics info is incorrect
>
>
> Key: KYLIN-4174
> URL: https://issues.apache.org/jira/browse/KYLIN-4174
> Project: Kylin
> Issue Type: Bug
>Reporter: ZhouKang
>Assignee: luguosheng
>Priority: Major
> Attachments: image-2019-09-27-12-27-50-336.png,
> image-2019-09-27-12-27-50-393.png, image3.png
>
>
> Kylin: master branch
> The job statistics info is incorrect. The number behind type is not equal to
> the size of job list.
> Step 1: login kylin webui, open the Monitor
> Step 2: refresh the web page
>
> You can see, the query params of RESTful API is wrong, projectName is "_null"
> {code:java}
> // code placeholder
> curl
> 'http://zjy-bigdata-prc-kylin04.bj:7070/kylin/api/jobs/overview?jobSearchMode=ALL=_null=1'
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (KYLIN-4174) job statistics info is incorrect
[
https://issues.apache.org/jira/browse/KYLIN-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
luguosheng reassigned KYLIN-4174:
-
Assignee: luguosheng
> job statistics info is incorrect
>
>
> Key: KYLIN-4174
> URL: https://issues.apache.org/jira/browse/KYLIN-4174
> Project: Kylin
> Issue Type: Bug
>Reporter: ZhouKang
>Assignee: luguosheng
>Priority: Major
> Attachments: image-2019-09-27-12-27-50-336.png,
> image-2019-09-27-12-27-50-393.png, image3.png
>
>
> Kylin: master branch
> The job statistics info is incorrect. The number behind type is not equal to
> the size of job list.
> Step 1: login kylin webui, open the Monitor
> Step 2: refresh the web page
>
> You can see, the query params of RESTful API is wrong, projectName is "_null"
> {code:java}
> // code placeholder
> curl
> 'http://zjy-bigdata-prc-kylin04.bj:7070/kylin/api/jobs/overview?jobSearchMode=ALL=_null=1'
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (KYLIN-4177) when unassign a Replica Set from a cube, can not reassign it in page.
luguosheng created KYLIN-4177: - Summary: when unassign a Replica Set from a cube, can not reassign it in page. Key: KYLIN-4177 URL: https://issues.apache.org/jira/browse/KYLIN-4177 Project: Kylin Issue Type: Improvement Reporter: luguosheng -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KYLIN-4173) cube list search can not work
[ https://issues.apache.org/jira/browse/KYLIN-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng updated KYLIN-4173: -- Description: In the font-end, service/cube.js add a new path "cubeName" in version d449335d68f01270aa0b6a8093ca12daff4b74bd like ''cubes/:cubeId/:propName/:propValue/:action/:cubeName''. this caused the list cube api "cubes?cubeName=xx" change to "cubes/xx" and match the wrong api. was: In the font-end, service/cube.js add a new path "cubeName" in version d449335d68f01270aa0b6a8093ca12daff4b74bd like ''cubes/:cubeId/:propName/:propValue/:action/:cubeName''. this caused the list cube api "cubes?cubeName=xx" change to "cubes/xx" and match the other api. > cube list search can not work > - > > Key: KYLIN-4173 > URL: https://issues.apache.org/jira/browse/KYLIN-4173 > Project: Kylin > Issue Type: Bug >Reporter: luguosheng >Assignee: luguosheng >Priority: Major > > In the font-end, service/cube.js add a new path "cubeName" in version > d449335d68f01270aa0b6a8093ca12daff4b74bd like > ''cubes/:cubeId/:propName/:propValue/:action/:cubeName''. > this caused the list cube api "cubes?cubeName=xx" change to "cubes/xx" and > match the wrong api. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KYLIN-4173) cube list search can not work
[ https://issues.apache.org/jira/browse/KYLIN-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng updated KYLIN-4173: -- Description: In the font-end, service/cube.js add a new path "cubeName" in version d449335d68f01270aa0b6a8093ca12daff4b74bd like ''cubes/:cubeId/:propName/:propValue/:action/:cubeName''. this caused the list cube api "cubes?cubeName=xx" change to "cubes/xx" and match the other api. was: In the font-end, service/cube.js add a new path "cubeName" in version d449335d68f01270aa0b6a8093ca12daff4b74bd like ''cubes/:cubeId/:propName/:propValue/:action/:cubeName'' this caused the list cube api "cubes?cubeName=xx" change to "cubes/xx" and match the other api. > cube list search can not work > - > > Key: KYLIN-4173 > URL: https://issues.apache.org/jira/browse/KYLIN-4173 > Project: Kylin > Issue Type: Bug >Reporter: luguosheng >Assignee: luguosheng >Priority: Major > > In the font-end, service/cube.js add a new path "cubeName" in version > d449335d68f01270aa0b6a8093ca12daff4b74bd like > ''cubes/:cubeId/:propName/:propValue/:action/:cubeName''. > this caused the list cube api "cubes?cubeName=xx" change to "cubes/xx" and > match the other api. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KYLIN-4173) cube list search can not work
[ https://issues.apache.org/jira/browse/KYLIN-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng updated KYLIN-4173: -- Description: In the font-end, service/cube.js add a new path "cubeName" in version d449335d68f01270aa0b6a8093ca12daff4b74bd like ''cubes/:cubeId/:propName/:propValue/:action/:cubeName'' this caused the list cube api "cubes?cubeName=xx" change to "cubes/xx" and match the other api. > cube list search can not work > - > > Key: KYLIN-4173 > URL: https://issues.apache.org/jira/browse/KYLIN-4173 > Project: Kylin > Issue Type: Bug >Reporter: luguosheng >Assignee: luguosheng >Priority: Major > > In the font-end, service/cube.js add a new path "cubeName" in version > d449335d68f01270aa0b6a8093ca12daff4b74bd like > ''cubes/:cubeId/:propName/:propValue/:action/:cubeName'' > this caused the list cube api "cubes?cubeName=xx" change to "cubes/xx" and > match the other api. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KYLIN-4173) cube list search can not work
luguosheng created KYLIN-4173: - Summary: cube list search can not work Key: KYLIN-4173 URL: https://issues.apache.org/jira/browse/KYLIN-4173 Project: Kylin Issue Type: Bug Reporter: luguosheng Assignee: luguosheng -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KYLIN-4159) The first step of build cube job will fail and throw "Column 'xx' in where clause is ambiguous" in jdbc datasource.
[ https://issues.apache.org/jira/browse/KYLIN-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng updated KYLIN-4159: -- Summary: The first step of build cube job will fail and throw "Column 'xx' in where clause is ambiguous" in jdbc datasource. (was: The first step of job will fail and throw "Column 'xx' in where clause is ambiguous" in jdbc datasource.) > The first step of build cube job will fail and throw "Column 'xx' in where > clause is ambiguous" in jdbc datasource. > --- > > Key: KYLIN-4159 > URL: https://issues.apache.org/jira/browse/KYLIN-4159 > Project: Kylin > Issue Type: Bug >Reporter: luguosheng >Assignee: luguosheng >Priority: Major > > Reappear: > In the model of kylin, If we have a column used as a partition column in the > fact table, and there is a column in lookup table has the same name. It can > be reappeared。 > RootCause: > In jdbc datasource , we use Sqoop option "--boundary-query sql" to split > data, the sql like "select max(partition_column), min(partition_column) from > flat_table where flat_table.partition_column> 20120101 and > flat_table.partition.column < 20190101" and there is more than one column > which have the same name of the "partition_column" in the flat_table. the sql > driver can not distinguish the table that partition_column belong to。 > How to resolve: > Alter the sql like: "select max(t.partition_column),min(t.partition_column) > from flat_table where flat_table.partition_column> 20120101 and > flat_table.partition.column < 20190101" > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (KYLIN-4159) The first step of job will fail and throw "Column 'xx' in where clause is ambiguous" in jdbc datasource.
[ https://issues.apache.org/jira/browse/KYLIN-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng updated KYLIN-4159: -- Description: Reappear: In the model of kylin, If we have a column used as a partition column in the fact table, and there is a column in lookup table has the same name. It can be reappeared。 RootCause: In jdbc datasource , we use Sqoop option "--boundary-query sql" to split data, the sql like "select max(partition_column), min(partition_column) from flat_table where flat_table.partition_column> 20120101 and flat_table.partition.column < 20190101" and there is more than one column which have the same name of the "partition_column" in the flat_table. the sql driver can not distinguish the table that partition_column belong to。 How to resolve: Alter the sql like: "select max(t.partition_column),min(t.partition_column) from flat_table where flat_table.partition_column> 20120101 and flat_table.partition.column < 20190101" was: Reappear: In the model of kylin, If we have a column used as a partition column in the fact table, and there is a column in lookup table has the same name. It can be reappeared。 RootCause: In jdbc datasource , we use Sqoop option "--boundary-query sql" to split data, the sql like "select max(partition_column), min(partition_column) from flat_table where flat_table.partition_column> 20120101 and flat_table.partition.column < 20190101" and there is more than one column which have the same name of the "partition_column" in the flat_table. the sql driver can not distinguish the table that partition_column belong to。 How to resolve: ^Alter the sql like: "select max(t.partition_column),min(t.partition_column) from flat_table where flat_table.partition_column> 20120101 and flat_table.partition.column < 20190101"^ > The first step of job will fail and throw "Column 'xx' in where clause is > ambiguous" in jdbc datasource. > > > Key: KYLIN-4159 > URL: https://issues.apache.org/jira/browse/KYLIN-4159 > Project: Kylin > Issue Type: Bug >Reporter: luguosheng >Assignee: luguosheng >Priority: Major > > Reappear: > In the model of kylin, If we have a column used as a partition column in the > fact table, and there is a column in lookup table has the same name. It can > be reappeared。 > RootCause: > In jdbc datasource , we use Sqoop option "--boundary-query sql" to split > data, the sql like "select max(partition_column), min(partition_column) from > flat_table where flat_table.partition_column> 20120101 and > flat_table.partition.column < 20190101" and there is more than one column > which have the same name of the "partition_column" in the flat_table. the sql > driver can not distinguish the table that partition_column belong to。 > How to resolve: > Alter the sql like: "select max(t.partition_column),min(t.partition_column) > from flat_table where flat_table.partition_column> 20120101 and > flat_table.partition.column < 20190101" > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (KYLIN-4159) The first step of job will fail and throw "Column 'xx' in where clause is ambiguous" in jdbc datasource.
luguosheng created KYLIN-4159: - Summary: The first step of job will fail and throw "Column 'xx' in where clause is ambiguous" in jdbc datasource. Key: KYLIN-4159 URL: https://issues.apache.org/jira/browse/KYLIN-4159 Project: Kylin Issue Type: Bug Reporter: luguosheng Assignee: luguosheng Reappear: In the model of kylin, If we have a column used as a partition column in the fact table, and there is a column in lookup table has the same name. It can be reappeared。 RootCause: In jdbc datasource , we use Sqoop option "--boundary-query sql" to split data, the sql like "select max(partition_column), min(partition_column) from flat_table where flat_table.partition_column> 20120101 and flat_table.partition.column < 20190101" and there is more than one column which have the same name of the "partition_column" in the flat_table. the sql driver can not distinguish the table that partition_column belong to。 How to resolve: ^Alter the sql like: "select max(t.partition_column),min(t.partition_column) from flat_table where flat_table.partition_column> 20120101 and flat_table.partition.column < 20190101"^ -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (KYLIN-4155) Cube status can not change immediately when executed disable or enable button in web
luguosheng created KYLIN-4155: - Summary: Cube status can not change immediately when executed disable or enable button in web Key: KYLIN-4155 URL: https://issues.apache.org/jira/browse/KYLIN-4155 Project: Kylin Issue Type: Bug Reporter: luguosheng Assignee: luguosheng When user execute disable or enable button in cube list dropdown menu , and then api response was back successfully, cube status tag can not change. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (KYLIN-4149) Allow user to edit streaming v2 table's kafka cluster address and topic name
luguosheng created KYLIN-4149: - Summary: Allow user to edit streaming v2 table's kafka cluster address and topic name Key: KYLIN-4149 URL: https://issues.apache.org/jira/browse/KYLIN-4149 Project: Kylin Issue Type: Improvement Reporter: luguosheng Assignee: luguosheng -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (KYLIN-4148) Execute 'bin/kylin-port-replace-util.sh' to change port will cause the configuration of 'kylin.metadata.url' lost
luguosheng created KYLIN-4148: - Summary: Execute 'bin/kylin-port-replace-util.sh' to change port will cause the configuration of 'kylin.metadata.url' lost Key: KYLIN-4148 URL: https://issues.apache.org/jira/browse/KYLIN-4148 Project: Kylin Issue Type: Bug Reporter: luguosheng Assignee: luguosheng -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (KYLIN-4139) Compatible old user security xml config when user upgrate new kylin version
[ https://issues.apache.org/jira/browse/KYLIN-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng updated KYLIN-4139: -- Description: Forward compatible # when user config 'spring.profiles.active=testing', sync old version user metadata with user config in kylinSecurity.xml Other improvement # Remove the logic of auto trans new user name to uppercase was: * Forward compatible # when user config 'spring.profiles.active=testing', sync old version user metadata with user config in kylinSecurity.xml * Other improvement # Remove the logic of auto trans new user name to uppercase > Compatible old user security xml config when user upgrate new kylin version > > > Key: KYLIN-4139 > URL: https://issues.apache.org/jira/browse/KYLIN-4139 > Project: Kylin > Issue Type: Improvement >Reporter: luguosheng >Assignee: luguosheng >Priority: Major > > Forward compatible > # when user config 'spring.profiles.active=testing', sync old version user > metadata with user config in kylinSecurity.xml > Other improvement > # Remove the logic of auto trans new user name to uppercase -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (KYLIN-4139) Compatible old user security xml config when user upgrate new kylin version
[ https://issues.apache.org/jira/browse/KYLIN-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng updated KYLIN-4139: -- Description: Forward compatible # when user config 'spring.profiles.active=testing', sync old version user metadata with user config in kylinSecurity.xml Other improvement # Remove the logic of auto trans new user name to uppercase was: Forward compatible # when user config 'spring.profiles.active=testing', sync old version user metadata with user config in kylinSecurity.xml Other improvement # Remove the logic of auto trans new user name to uppercase > Compatible old user security xml config when user upgrate new kylin version > > > Key: KYLIN-4139 > URL: https://issues.apache.org/jira/browse/KYLIN-4139 > Project: Kylin > Issue Type: Improvement >Reporter: luguosheng >Assignee: luguosheng >Priority: Major > > > Forward compatible > # when user config 'spring.profiles.active=testing', sync old version user > metadata with user config in kylinSecurity.xml > Other improvement > # Remove the logic of auto trans new user name to uppercase -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (KYLIN-4139) Compatible old user security xml config when user upgrate new kylin version
[ https://issues.apache.org/jira/browse/KYLIN-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng updated KYLIN-4139: -- Description: * Forward compatible # when user config 'spring.profiles.active=testing', sync old version user metadata with user config in kylinSecurity.xml * Other improvement # Remove the logic of auto trans new user name to uppercase > Compatible old user security xml config when user upgrate new kylin version > > > Key: KYLIN-4139 > URL: https://issues.apache.org/jira/browse/KYLIN-4139 > Project: Kylin > Issue Type: Improvement >Reporter: luguosheng >Assignee: luguosheng >Priority: Major > > * Forward compatible > # when user config 'spring.profiles.active=testing', sync old version user > metadata with user config in kylinSecurity.xml > * Other improvement > # Remove the logic of auto trans new user name to uppercase -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (KYLIN-4139) Compatible old user security xml config when user upgrate new kylin version
luguosheng created KYLIN-4139: - Summary: Compatible old user security xml config when user upgrate new kylin version Key: KYLIN-4139 URL: https://issues.apache.org/jira/browse/KYLIN-4139 Project: Kylin Issue Type: Improvement Reporter: luguosheng Assignee: luguosheng -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (KYLIN-4126) cube name validate code cause the wrong judge of streaming type
luguosheng created KYLIN-4126: - Summary: cube name validate code cause the wrong judge of streaming type Key: KYLIN-4126 URL: https://issues.apache.org/jira/browse/KYLIN-4126 Project: Kylin Issue Type: Bug Reporter: luguosheng Assignee: luguosheng -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (KYLIN-4122) Add kylin user and group manage modules
luguosheng created KYLIN-4122: - Summary: Add kylin user and group manage modules Key: KYLIN-4122 URL: https://issues.apache.org/jira/browse/KYLIN-4122 Project: Kylin Issue Type: New Feature Reporter: luguosheng Assignee: luguosheng -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (KYLIN-4091) support fast mode and simple mode for running CI
[ https://issues.apache.org/jira/browse/KYLIN-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng updated KYLIN-4091: -- Description: -DfastBuildMode = true // build or merge job in concurrent queue -DsimpleBuildMode = true // skip merge job and just build only one segment was: -DfastBuildMode = true // build or merge job in concurrent queue -DsimpleBuildMode = true // skip merge job > support fast mode and simple mode for running CI > > > Key: KYLIN-4091 > URL: https://issues.apache.org/jira/browse/KYLIN-4091 > Project: Kylin > Issue Type: Improvement >Reporter: luguosheng >Assignee: luguosheng >Priority: Major > > -DfastBuildMode = true // build or merge job in concurrent queue > -DsimpleBuildMode = true // skip merge job and just build only one segment -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (KYLIN-4091) support fast mode and simple mode for running CI
[ https://issues.apache.org/jira/browse/KYLIN-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng updated KYLIN-4091: -- Description: -DfastBuildMode = true // build or merge job in concurrent queue -DsimpleBuildMode = true // skip merge job > support fast mode and simple mode for running CI > > > Key: KYLIN-4091 > URL: https://issues.apache.org/jira/browse/KYLIN-4091 > Project: Kylin > Issue Type: Improvement >Reporter: luguosheng >Assignee: luguosheng >Priority: Major > > -DfastBuildMode = true // build or merge job in concurrent queue > -DsimpleBuildMode = true // skip merge job -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (KYLIN-4091) support fast mode and simple mode for running CI
luguosheng created KYLIN-4091: - Summary: support fast mode and simple mode for running CI Key: KYLIN-4091 URL: https://issues.apache.org/jira/browse/KYLIN-4091 Project: Kylin Issue Type: Improvement Reporter: luguosheng Assignee: luguosheng -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (KYLIN-3942) Rea-time OLAP don't support multi-level json event
[
https://issues.apache.org/jira/browse/KYLIN-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
luguosheng reassigned KYLIN-3942:
-
Assignee: luguosheng (was: XiaoXiang Yu)
> Rea-time OLAP don't support multi-level json event
> --
>
> Key: KYLIN-3942
> URL: https://issues.apache.org/jira/browse/KYLIN-3942
> Project: Kylin
> Issue Type: Bug
> Components: Real-time Streaming
>Affects Versions: v3.0.0-alpha
>Reporter: XiaoXiang Yu
>Assignee: luguosheng
>Priority: Critical
>
> Currently real-time OLAP didn't support multi-level json event.
> For example,if I have a kafka multi-level json event like this:
> {quote}{"country":"JAPAN","amount":13.075058425023922,"qty":8,"currency":"USD","order_time":1554801950882,"category":"ELECTRONIC","device":"Andriod","user":\{"gender":"Female","id":"7a0cfa5e-bbaa-79ef-1a38-e06f02c85fcb","first_name":"unknown","age":16}}
> {quote}
>
> Receiver will throw exception like this and discard that event:
>
> {quote}2019-04-09 09:46:09,878 ERROR [StreamingV2Cube_channel]
> kafka.TimedJsonStreamParser:107 : error
> com.fasterxml.jackson.databind.exc.MismatchedInputException: Cannot
> deserialize instance of `java.lang.String` out of START_OBJECT token
> at [Source:
> (String)"\{"country":"US","amount":14.498498222823619,"qty":1,"currency":"USD","order_time":1554803169876,"category":"Other","device":"Other","user":{"gender":"Female","id":"0736b41a-9ae7-9b4a-a124-f74436d3eb41","first_name":"unknown","age":26}}";
> line: 1, column: 140] (through reference chain: java.util.HashMap["user"])
> at
> com.fasterxml.jackson.databind.exc.MismatchedInputException.from(MismatchedInputException.java:63)
> at
> com.fasterxml.jackson.databind.DeserializationContext.reportInputMismatch(DeserializationContext.java:1342)
> at
> com.fasterxml.jackson.databind.DeserializationContext.handleUnexpectedToken(DeserializationContext.java:1138)
> at
> com.fasterxml.jackson.databind.DeserializationContext.handleUnexpectedToken(DeserializationContext.java:1092)
> at
> com.fasterxml.jackson.databind.deser.std.StringDeserializer.deserialize(StringDeserializer.java:63)
> at
> com.fasterxml.jackson.databind.deser.std.StringDeserializer.deserialize(StringDeserializer.java:10)
> at
> com.fasterxml.jackson.databind.deser.std.MapDeserializer._readAndBindStringKeyMap(MapDeserializer.java:527)
> at
> com.fasterxml.jackson.databind.deser.std.MapDeserializer.deserialize(MapDeserializer.java:364)
> at
> com.fasterxml.jackson.databind.deser.std.MapDeserializer.deserialize(MapDeserializer.java:29)
> at
> com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:4001)
> at
> com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3030)
> at
> org.apache.kylin.stream.source.kafka.TimedJsonStreamParser.parse(TimedJsonStreamParser.java:79)
> at
> org.apache.kylin.stream.source.kafka.TimedJsonStreamParser.parse(TimedJsonStreamParser.java:54)
> at
> org.apache.kylin.stream.source.kafka.consumer.KafkaConnector.nextEvent(KafkaConnector.java:110)
> at
> org.apache.kylin.stream.core.consumer.StreamingConsumerChannel.run(StreamingConsumerChannel.java:93)
> at java.lang.Thread.run(Thread.java:748)
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KYLIN-3440) Couldn't merge if there is an empty segment
[
https://issues.apache.org/jira/browse/KYLIN-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
luguosheng resolved KYLIN-3440.
---
Resolution: Resolved
Assignee: luguosheng
Fix Version/s: v2.3.0
v2.4.0
> Couldn't merge if there is an empty segment
> ---
>
> Key: KYLIN-3440
> URL: https://issues.apache.org/jira/browse/KYLIN-3440
> Project: Kylin
> Issue Type: Bug
> Components: Web
>Affects Versions: v2.3.1, v2.4.0
>Reporter: Shaofeng SHI
>Assignee: luguosheng
>Priority: Major
> Fix For: v2.4.0, v2.3.0
>
> Attachments: 2018-07-04 上午8.42.08.png
>
>
> I have a cube which has empty segment (actually the segment is not empty,
> just because the job counter wasn't fetched). When I try to merge the
> segments, Kylin reports error, asking me if I want to continue forcely; When
> click "yes", the same error be reported. From the http request, I didn't see
> the "forceMergeEmptySegment" parameter was set.
> {code:java}
> org.apache.kylin.rest.exception.InternalErrorException: Empty cube segment
> found, couldn't merge unless 'forceMergeEmptySegment' set to true:
> [2012010100_2012080100, 2012080100_2018070100]
> at
> org.apache.kylin.rest.controller.CubeController.buildInternal(CubeController.java:416)
> at
> org.apache.kylin.rest.controller.CubeController.rebuild(CubeController.java:366)
> 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:205)
> at
> org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:133)
> at
> org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:97)
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:827)
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:738)
> at
> org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)
> at
> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:967)
> at
> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:901)
> at
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:970)
> at
> org.springframework.web.servlet.FrameworkServlet.doPut(FrameworkServlet.java:883)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:653)
> at
> org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3116) Fix cardinality caculate checkbox issue when loading tables
[ https://issues.apache.org/jira/browse/KYLIN-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16340622#comment-16340622 ] luguosheng commented on KYLIN-3116: --- has reviewed > Fix cardinality caculate checkbox issue when loading tables > --- > > Key: KYLIN-3116 > URL: https://issues.apache.org/jira/browse/KYLIN-3116 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.2.0 > Environment: Centos 7, ambari, HDP 2.6 >Reporter: vu thanh dat >Assignee: Zhixiong Chen >Priority: Major > Labels: build > Fix For: v2.3.0 > > Attachments: > 0001-KYLIN-3116-Fix-cardinality-caculate-checkbox-issue-w.patch, > mapreduce.bmp, 屏幕快照 2017-12-19 上午10.31.06.png > > > Hi all, > im using Kylin to speed up query HDFS. > Which 2.5 billions records per day. When i'm using Kylin and load hive table, > it make a mapreduce on my server, 2969 map and 1 reduce with only 1 table. My > datasource about 10 tables. And it so slow. I attached an image. > So, can i speed up process "Load hive table" to create model and cubes so > quickly? > Exam use spark (because mapreduce so slow)? > Best regards, Thanks all -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-2918) Table ACL needs GUI
[ https://issues.apache.org/jira/browse/KYLIN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng updated KYLIN-2918: -- Attachment: 0001-KYLIN-2918-table-acl-gui.patch > Table ACL needs GUI > --- > > Key: KYLIN-2918 > URL: https://issues.apache.org/jira/browse/KYLIN-2918 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.2.0 >Reporter: liyang >Assignee: luguosheng > Labels: scope > Fix For: v2.3.0 > > Attachments: 0001-KYLIN-2918-table-acl-gui.patch > > > The backend of Table ACL is done, but the GUI part still requires work. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-3067) Provide web interface for dimension capping feature
[ https://issues.apache.org/jira/browse/KYLIN-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277896#comment-16277896 ] luguosheng commented on KYLIN-3067: --- reviewed > Provide web interface for dimension capping feature > --- > > Key: KYLIN-3067 > URL: https://issues.apache.org/jira/browse/KYLIN-3067 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Roger Shi >Assignee: Zhixiong Chen > Attachments: 0001-KYLIN-3067-provide-dim-cap-in-GUL.patch > > > As [KYLIN-2363] has provided the dimension capping feature in the backend, we > need a proper web interface. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2963) Remove Beta for Spark Cubing
[ https://issues.apache.org/jira/browse/KYLIN-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng resolved KYLIN-2963. --- Resolution: Fixed Assignee: luguosheng > Remove Beta for Spark Cubing > > > Key: KYLIN-2963 > URL: https://issues.apache.org/jira/browse/KYLIN-2963 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v2.2.0 >Reporter: Dong Li >Assignee: luguosheng > Fix For: v2.2.0 > > > We shipped Spark Cubing(Beta) since v2.0 release, and now it's getting more > stable. More and more users have adopted spark cubing on production > environment. It's time to remove the "Beta" label. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2947) Changed the Pop-up box when no project selected
[ https://issues.apache.org/jira/browse/KYLIN-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng resolved KYLIN-2947. --- Resolution: Fixed Fix Version/s: v2.3.0 > Changed the Pop-up box when no project selected > --- > > Key: KYLIN-2947 > URL: https://issues.apache.org/jira/browse/KYLIN-2947 > Project: Kylin > Issue Type: Improvement >Affects Versions: v2.3.0 >Reporter: peng.jianhua >Assignee: peng.jianhua > Fix For: v2.3.0 > > Attachments: > 0001-KYLIN-2947-Changed-the-Pop-up-box-when-no-project-se.patch, 01.PNG, > 02.PNG, 03.PNG > > > I noticed that the Pop-up box was like 01.png when there is no project > selected after you click the 'Calculate Cardinality',it reminds us we should > choose project first after we input the tablename and click the 'Calculate > Cardinality'. > And it keeps 'please wait' status on my environment after input and click > like 02.png. > It's unproperly.We should ingore this step,point out that there is no project > selected directly after we click the 'Calculate Cardinality',just like 03.png. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2756) Let "LIMIT" be optional in "Inspect" page
[ https://issues.apache.org/jira/browse/KYLIN-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng resolved KYLIN-2756. --- Resolution: Fixed > Let "LIMIT" be optional in "Inspect" page > - > > Key: KYLIN-2756 > URL: https://issues.apache.org/jira/browse/KYLIN-2756 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Attachments: > 0001-KYLIN-2756-Let-LIMIT-be-optional-in-inspect-page.patch > > > Kylin's "Inspect" page will append a LIMIT clause for queries if the query > doesn't have "LIMIT"; > While this will make some query be invalid because "LIMIT" not always appear > in the last position. For example: > select * from KYLIN_SALES OFFSET 100 ROWS FETCH FIRST 10 ROWS ONLY > According to Calcite's SQL reference, LIMIT should be before OFFSET clause. > So, Kylin should give user the option of not append the "LIMIT". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2947) Changed the Pop-up box when no project selected
[ https://issues.apache.org/jira/browse/KYLIN-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16210773#comment-16210773 ] luguosheng commented on KYLIN-2947: --- Thanks for your patch, I will merge it soon! > Changed the Pop-up box when no project selected > --- > > Key: KYLIN-2947 > URL: https://issues.apache.org/jira/browse/KYLIN-2947 > Project: Kylin > Issue Type: Improvement >Affects Versions: v2.3.0 >Reporter: peng.jianhua >Assignee: peng.jianhua > Attachments: > 0001-KYLIN-2947-Changed-the-Pop-up-box-when-no-project-se.patch, 01.PNG, > 02.PNG, 03.PNG > > > I noticed that the Pop-up box was like 01.png when there is no project > selected after you click the 'Calculate Cardinality',it reminds us we should > choose project first after we input the tablename and click the 'Calculate > Cardinality'. > And it keeps 'please wait' status on my environment after input and click > like 02.png. > It's unproperly.We should ingore this step,point out that there is no project > selected directly after we click the 'Calculate Cardinality',just like 03.png. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-1446) Visualization in Kylin Insight page doesn't work for line chart
[ https://issues.apache.org/jira/browse/KYLIN-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16209102#comment-16209102 ] luguosheng commented on KYLIN-1446: --- In query api response body, you can find a key named columnType. if it's value equals 91 or 92 or 93, it is a date type column; and -1, 1, 12 is a string type column，and -7, -6, -5, 3, 4, 5, 6, 7, 8 is a number type column. so we will set date or string type columns as dimension columns , and number type columns as measures. pls check the columnType in your response. maybe there was no dimensions in your query response. > Visualization in Kylin Insight page doesn't work for line chart > --- > > Key: KYLIN-1446 > URL: https://issues.apache.org/jira/browse/KYLIN-1446 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.5.0, v1.4.0 > Environment: PRODUCTION >Reporter: Hao Chen >Assignee: Zhong,Jason > > Visualization with Line chart in Kylin Insight page doesn't work. > When submitting a query to kylin on insight page, and select chart type as > line chart, the option selection controller doesn't allow to choose dimension > while metric selection works. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2335) http request always use cache data in IE10 or IE11
[ https://issues.apache.org/jira/browse/KYLIN-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng resolved KYLIN-2335. --- Resolution: Resolved Assignee: luguosheng (was: Zhong,Jason) Fix Version/s: v2.0.0 > http request always use cache data in IE10 or IE11 > --- > > Key: KYLIN-2335 > URL: https://issues.apache.org/jira/browse/KYLIN-2335 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.0.0 >Reporter: luguosheng >Assignee: luguosheng > Fix For: v2.0.0 > > > http request always use cache data in IE10 or IE11 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2920) Failed to get streaming config on WebUI
[ https://issues.apache.org/jira/browse/KYLIN-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng updated KYLIN-2920: -- Attachment: 0001-KYLIN-2920-Failed-to-get-streaming-config-on-WebUI.patch > Failed to get streaming config on WebUI > --- > > Key: KYLIN-2920 > URL: https://issues.apache.org/jira/browse/KYLIN-2920 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.2.0 >Reporter: Dong Li >Assignee: luguosheng > Fix For: v2.2.0 > > Attachments: > 0001-KYLIN-2920-Failed-to-get-streaming-config-on-WebUI.patch, Screen Shot > 2017-10-09 at 10.09.32.png > > > Paramters "project" of rest api call /kylin/api/streaming/getConfig are > missed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2855) column of BIGINT is not treat as dimensions for chart
[ https://issues.apache.org/jira/browse/KYLIN-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160319#comment-16160319 ] luguosheng commented on KYLIN-2855: --- In query api response body, you can find a key named columnType. if it's value equals 91 or 92 or 93, it is a date type column; and -1, 1, 12 is a string type column，and -7, -6, -5, 3, 4, 5, 6, 7, 8 is a number type column. so we will set date or string type columns as dimension columns , and number type columns as measures. pls check the columnType in your response. > column of BIGINT is not treat as dimensions for chart > - > > Key: KYLIN-2855 > URL: https://issues.apache.org/jira/browse/KYLIN-2855 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: Yang Hao >Assignee: Zhong,Jason > Attachments: screenshot-1.png > > > My query has appid,date, model, userNum, but the appid、date is not treat as > dimension but metrics -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2795) Improve REST API document, add get/list jobs
[ https://issues.apache.org/jira/browse/KYLIN-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng updated KYLIN-2795: -- Attachment: 0001-KYLIN-2795-Improve-REST-API-document-add-get-list-jo.patch > Improve REST API document, add get/list jobs > > > Key: KYLIN-2795 > URL: https://issues.apache.org/jira/browse/KYLIN-2795 > Project: Kylin > Issue Type: Improvement >Reporter: liyang >Assignee: luguosheng > Labels: scope > Attachments: > 0001-KYLIN-2795-Improve-REST-API-document-add-get-list-jo.patch > > > All job REST API requires jobid, but currently there is no API documented to > get/list existing Jobs. > http://kylin.apache.org/docs20/howto/howto_use_restapi.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (KYLIN-2795) Improve REST API document, add get/list jobs
[ https://issues.apache.org/jira/browse/KYLIN-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng reassigned KYLIN-2795: - Assignee: luguosheng > Improve REST API document, add get/list jobs > > > Key: KYLIN-2795 > URL: https://issues.apache.org/jira/browse/KYLIN-2795 > Project: Kylin > Issue Type: Improvement >Reporter: liyang >Assignee: luguosheng > Labels: scope > > All job REST API requires jobid, but currently there is no API documented to > get/list existing Jobs. > http://kylin.apache.org/docs20/howto/howto_use_restapi.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (KYLIN-1683) Row key could drag and drop in view state of cube - advanced settings tabpage
[ https://issues.apache.org/jira/browse/KYLIN-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng reassigned KYLIN-1683: - Assignee: luguosheng (was: Zhong,Jason) > Row key could drag and drop in view state of cube - advanced settings tabpage > - > > Key: KYLIN-1683 > URL: https://issues.apache.org/jira/browse/KYLIN-1683 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.5.1 >Reporter: Dong Li >Assignee: luguosheng >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-2689) Only dimension columns can join when create a model
luguosheng created KYLIN-2689: - Summary: Only dimension columns can join when create a model Key: KYLIN-2689 URL: https://issues.apache.org/jira/browse/KYLIN-2689 Project: Kylin Issue Type: Improvement Components: Web Affects Versions: v2.1.0 Reporter: luguosheng Assignee: luguosheng Fix For: v2.1.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2673) Should allow user to change fact table as long as the cube is disable
[ https://issues.apache.org/jira/browse/KYLIN-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052750#comment-16052750 ] luguosheng commented on KYLIN-2673: --- it is limited to change if it has cubes ，otherwise it will cause something wrong in cube > Should allow user to change fact table as long as the cube is disable > - > > Key: KYLIN-2673 > URL: https://issues.apache.org/jira/browse/KYLIN-2673 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.0.0 >Reporter: kangkaisen >Assignee: kangkaisen > Fix For: v2.1.0 > > > Currently, user couldn't change fact table even though the cube is disable, > which isn't reasonable. We should allow user to change fact table as long as > the cube is disable. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (KYLIN-2432) Couldn't select partition column in some old browser (such as Google Chrome 18.0.1025.162)
[ https://issues.apache.org/jira/browse/KYLIN-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng closed KYLIN-2432. - > Couldn't select partition column in some old browser (such as Google Chrome > 18.0.1025.162) > -- > > Key: KYLIN-2432 > URL: https://issues.apache.org/jira/browse/KYLIN-2432 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.0.0 >Reporter: luguosheng >Assignee: luguosheng > Fix For: v2.0.0 > > > Couldn't select partition column in some old browser (such as Google Chrome > 18.0.1025.162) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (KYLIN-2432) Couldn't select partition column in some old browser (such as Google Chrome 18.0.1025.162)
[ https://issues.apache.org/jira/browse/KYLIN-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng resolved KYLIN-2432. --- Resolution: Fixed > Couldn't select partition column in some old browser (such as Google Chrome > 18.0.1025.162) > -- > > Key: KYLIN-2432 > URL: https://issues.apache.org/jira/browse/KYLIN-2432 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.0.0 >Reporter: luguosheng >Assignee: luguosheng > Fix For: v2.0.0 > > > Couldn't select partition column in some old browser (such as Google Chrome > 18.0.1025.162) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KYLIN-2508) Trans the time to UTC time when set the range of building cube
luguosheng created KYLIN-2508: - Summary: Trans the time to UTC time when set the range of building cube Key: KYLIN-2508 URL: https://issues.apache.org/jira/browse/KYLIN-2508 Project: Kylin Issue Type: Bug Components: Website Affects Versions: v1.6.0 Reporter: luguosheng Assignee: luguosheng Fix For: v2.0.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KYLIN-2432) Couldn't select partition column in some old browser (such as Google Chrome 18.0.1025.162)
luguosheng created KYLIN-2432: - Summary: Couldn't select partition column in some old browser (such as Google Chrome 18.0.1025.162) Key: KYLIN-2432 URL: https://issues.apache.org/jira/browse/KYLIN-2432 Project: Kylin Issue Type: Bug Components: Web Affects Versions: v2.0.0 Reporter: luguosheng Assignee: luguosheng Fix For: v2.0.0 Couldn't select partition column in some old browser (such as Google Chrome 18.0.1025.162) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (KYLIN-2297) Manually edit cube segment start/end time will throw error in UI
[ https://issues.apache.org/jira/browse/KYLIN-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng closed KYLIN-2297. - Resolution: Fixed Fix Version/s: v2.0.0 > Manually edit cube segment start/end time will throw error in UI > > > Key: KYLIN-2297 > URL: https://issues.apache.org/jira/browse/KYLIN-2297 > Project: Kylin > Issue Type: Bug >Reporter: Yifan Zhang >Assignee: luguosheng > Fix For: v2.0.0 > > > Error message returned: > Could not read JSON: Can not construct instance of long from String value > '2012-01-01 01:05:05': not a valid Long value > at [Source: org.apache.catalina.connector.CoyoteInputStream@44aae22; line: 1, > column: 47] (through reference chain: > org.apache.kylin.rest.request.JobBuildRequest["endTime"]); nested exception > is com.fasterxml.jackson.databind.exc.InvalidFormatException: Can not > construct instance of long from String value '2012-01-01 01:05:05': not a > valid Long value > at [Source: org.apache.catalina.connector.CoyoteInputStream@44aae22; line: 1, > column: 47] (through reference chain: > org.apache.kylin.rest.request.JobBuildRequest["endTime"]) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (KYLIN-2298) timer component get wrong seconds
[ https://issues.apache.org/jira/browse/KYLIN-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng closed KYLIN-2298. - Resolution: Fixed > timer component get wrong seconds > - > > Key: KYLIN-2298 > URL: https://issues.apache.org/jira/browse/KYLIN-2298 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.0.0 >Reporter: luguosheng >Assignee: luguosheng > Fix For: v2.0.0 > > > in angular directive "dateTimepickerTimezone" , when get the seconds,lose > the timer object,it will cause problem when seconds greater than 10 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (KYLIN-2275) Remove dimensions cause wrong remove in advance settings
[ https://issues.apache.org/jira/browse/KYLIN-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng closed KYLIN-2275. - Resolution: Fixed > Remove dimensions cause wrong remove in advance settings > > > Key: KYLIN-2275 > URL: https://issues.apache.org/jira/browse/KYLIN-2275 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.6.0 >Reporter: luguosheng >Assignee: luguosheng > Fix For: v2.0.0 > > > Remove dimensions cause wrong remove in advance settings(Mandatory > Dimensions,Hierarchy Dimensions,Joint Dimensions), -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2298) timer component get wrong seconds
luguosheng created KYLIN-2298: - Summary: timer component get wrong seconds Key: KYLIN-2298 URL: https://issues.apache.org/jira/browse/KYLIN-2298 Project: Kylin Issue Type: Bug Components: Web Affects Versions: v1.6.1 Reporter: luguosheng Assignee: luguosheng Fix For: v1.6.1 in angular directive "dateTimepickerTimezone" , when get the seconds,lose the timer object,it will cause problem when seconds greater than 10 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2275) Remove dimensions cause wrong remove in advance settings
[ https://issues.apache.org/jira/browse/KYLIN-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng updated KYLIN-2275: -- Description: Remove dimensions cause wrong remove in advance settings(Mandatory Dimensions,Hierarchy Dimensions,Joint Dimensions), (was: Remove dimensions cause wrong remove in advance settings) > Remove dimensions cause wrong remove in advance settings > > > Key: KYLIN-2275 > URL: https://issues.apache.org/jira/browse/KYLIN-2275 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.6.0 >Reporter: luguosheng >Assignee: luguosheng > Fix For: v1.6.1 > > > Remove dimensions cause wrong remove in advance settings(Mandatory > Dimensions,Hierarchy Dimensions,Joint Dimensions), -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2275) Remove dimensions cause wrong remove in advance settings
luguosheng created KYLIN-2275: - Summary: Remove dimensions cause wrong remove in advance settings Key: KYLIN-2275 URL: https://issues.apache.org/jira/browse/KYLIN-2275 Project: Kylin Issue Type: Bug Components: Web Affects Versions: v1.6.0 Reporter: luguosheng Assignee: luguosheng Fix For: v1.6.1 Remove dimensions cause wrong remove in advance settings -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2082) Support to change streaming configuration
[ https://issues.apache.org/jira/browse/KYLIN-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng updated KYLIN-2082: -- Attachment: 0001-change-streaming-configuration.patch please help me to review patch > Support to change streaming configuration > - > > Key: KYLIN-2082 > URL: https://issues.apache.org/jira/browse/KYLIN-2082 > Project: Kylin > Issue Type: Improvement > Components: streaming, Web >Reporter: Shaofeng SHI >Assignee: Zhong,Jason > Fix For: v1.6.0 > > Attachments: 0001-change-streaming-configuration.patch > > > So far after create/save a streaming table, user couldn't edit it. Change > should be supported as it is very common to change some info like cluster or > parser properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
