[jira] [Commented] (KYLIN-3058) We should limit the integer type ID and Port for "Kafka Setting" in "Streaming Cluster" page
[
https://issues.apache.org/jira/browse/KYLIN-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16268110#comment-16268110
]
peng.jianhua commented on KYLIN-3058:
-
Hi [~Zhixiong Chen], I have checked the all web pages, and find the other input
limition issues, refer to
[^advanced_setting(supplement).png][^kafka_setting(supplement).png][^measures(supplement).png].
Then I repaired them, and update the patch, please check it, thanks!
> We should limit the integer type ID and Port for "Kafka Setting" in
> "Streaming Cluster" page
>
>
> Key: KYLIN-3058
> URL: https://issues.apache.org/jira/browse/KYLIN-3058
> Project: Kylin
> Issue Type: Bug
> Components: Web
>Reporter: peng.jianhua
>Assignee: peng.jianhua
> Labels: patch
> Fix For: v2.3.0
>
> Attachments:
> 0001-KYLIN-3058-We-should-limit-the-integer-type-ID-and-P.patch,
> advanced_setting(supplement).png, create_non_interger_ID.png,
> edit_non_interger_ID.png, kafka_setting(supplement).png,
> measures(supplement).png, streaming_table_dashboard.png
>
>
> When you create or edit one streaming table, then set a non-integer type ID
> for "Kafka Setting" in "Streaming Cluster" page( refer to
> [^streaming_table_dashboard.png]), at last save it, you will find an error
> message page will pop up.
> 1. Create a streaming table, then set a non-integer type ID to save, such as
> "23a", you will get the error message page, refer to
> [^create_non_interger_ID.png];
> 2. Edit a streaming table, then modify a non-integer type ID to save, such as
> "23a", you will also get another error message page, refer to
> [^edit_non_interger_ID.png];
> In order to find out the cause of the problem, I analyze the Kylin server
> log, then I find the error, as follow:
> {panel:title=Kylin server log}
> 2017-11-24 18:46:07,413 ERROR [http-bio-7070-exec-14]
> controller.StreamingController:280 : The data KafkaConfig definition is
> invalid.
> {color:red}com.fasterxml.jackson.databind.exc.InvalidFormatException: Can not
> construct instance of int from String value '23a': not a valid Integer
> value{color}
> at [Source:
> {"uuid":"261e36cd-599e-4306-93b2-add0291de588","last_modified":1511520352482,"version":"2.3.0.20500","name":"DEFAULT.STREAMING_TABLE","clusters":[{"uuid":null,"last_modified":0,"version":"2.3.0.20500","brokers":[{"id":"23a","host":"1","port":1}],"newBroker":{"id":"23a","host":"1","port":1}}],"topic":"kafka
>
> topic","timeout":6,"parserName":"org.apache.kylin.source.kafka.TimedJsonStreamParser","timestampField":null,"margin":0,"parserProperties":"tsColName=datetime"};
> {panel}
> Then I find the server code, it also show the ID and Port must be integer, as
> follow:
> {code:java}
> public class BrokerConfig implements Serializable{
> @JsonProperty("id")
> private int id;
> ..
> @JsonProperty("port")
> private int port;
> {code}
> It means the parameter ID and Port are both not allowed for non-integer
> types, so we should solve them at the web page.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KYLIN-3058) We should limit the integer type ID and Port for "Kafka Setting" in "Streaming Cluster" page
[
https://issues.apache.org/jira/browse/KYLIN-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
peng.jianhua updated KYLIN-3058:
Attachment: 0001-KYLIN-3058-We-should-limit-the-integer-type-ID-and-P.patch
> We should limit the integer type ID and Port for "Kafka Setting" in
> "Streaming Cluster" page
>
>
> Key: KYLIN-3058
> URL: https://issues.apache.org/jira/browse/KYLIN-3058
> Project: Kylin
> Issue Type: Bug
> Components: Web
>Reporter: peng.jianhua
>Assignee: peng.jianhua
> Labels: patch
> Fix For: v2.3.0
>
> Attachments:
> 0001-KYLIN-3058-We-should-limit-the-integer-type-ID-and-P.patch,
> advanced_setting(supplement).png, create_non_interger_ID.png,
> edit_non_interger_ID.png, kafka_setting(supplement).png,
> measures(supplement).png, streaming_table_dashboard.png
>
>
> When you create or edit one streaming table, then set a non-integer type ID
> for "Kafka Setting" in "Streaming Cluster" page( refer to
> [^streaming_table_dashboard.png]), at last save it, you will find an error
> message page will pop up.
> 1. Create a streaming table, then set a non-integer type ID to save, such as
> "23a", you will get the error message page, refer to
> [^create_non_interger_ID.png];
> 2. Edit a streaming table, then modify a non-integer type ID to save, such as
> "23a", you will also get another error message page, refer to
> [^edit_non_interger_ID.png];
> In order to find out the cause of the problem, I analyze the Kylin server
> log, then I find the error, as follow:
> {panel:title=Kylin server log}
> 2017-11-24 18:46:07,413 ERROR [http-bio-7070-exec-14]
> controller.StreamingController:280 : The data KafkaConfig definition is
> invalid.
> {color:red}com.fasterxml.jackson.databind.exc.InvalidFormatException: Can not
> construct instance of int from String value '23a': not a valid Integer
> value{color}
> at [Source:
> {"uuid":"261e36cd-599e-4306-93b2-add0291de588","last_modified":1511520352482,"version":"2.3.0.20500","name":"DEFAULT.STREAMING_TABLE","clusters":[{"uuid":null,"last_modified":0,"version":"2.3.0.20500","brokers":[{"id":"23a","host":"1","port":1}],"newBroker":{"id":"23a","host":"1","port":1}}],"topic":"kafka
>
> topic","timeout":6,"parserName":"org.apache.kylin.source.kafka.TimedJsonStreamParser","timestampField":null,"margin":0,"parserProperties":"tsColName=datetime"};
> {panel}
> Then I find the server code, it also show the ID and Port must be integer, as
> follow:
> {code:java}
> public class BrokerConfig implements Serializable{
> @JsonProperty("id")
> private int id;
> ..
> @JsonProperty("port")
> private int port;
> {code}
> It means the parameter ID and Port are both not allowed for non-integer
> types, so we should solve them at the web page.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KYLIN-3058) We should limit the integer type ID and Port for "Kafka Setting" in "Streaming Cluster" page
[
https://issues.apache.org/jira/browse/KYLIN-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
peng.jianhua updated KYLIN-3058:
Attachment: (was:
0001-KYLIN-3058-We-should-limit-the-integer-type-ID-for-K.patch)
> We should limit the integer type ID and Port for "Kafka Setting" in
> "Streaming Cluster" page
>
>
> Key: KYLIN-3058
> URL: https://issues.apache.org/jira/browse/KYLIN-3058
> Project: Kylin
> Issue Type: Bug
> Components: Web
>Reporter: peng.jianhua
>Assignee: peng.jianhua
> Labels: patch
> Fix For: v2.3.0
>
> Attachments: advanced_setting(supplement).png,
> create_non_interger_ID.png, edit_non_interger_ID.png,
> kafka_setting(supplement).png, measures(supplement).png,
> streaming_table_dashboard.png
>
>
> When you create or edit one streaming table, then set a non-integer type ID
> for "Kafka Setting" in "Streaming Cluster" page( refer to
> [^streaming_table_dashboard.png]), at last save it, you will find an error
> message page will pop up.
> 1. Create a streaming table, then set a non-integer type ID to save, such as
> "23a", you will get the error message page, refer to
> [^create_non_interger_ID.png];
> 2. Edit a streaming table, then modify a non-integer type ID to save, such as
> "23a", you will also get another error message page, refer to
> [^edit_non_interger_ID.png];
> In order to find out the cause of the problem, I analyze the Kylin server
> log, then I find the error, as follow:
> {panel:title=Kylin server log}
> 2017-11-24 18:46:07,413 ERROR [http-bio-7070-exec-14]
> controller.StreamingController:280 : The data KafkaConfig definition is
> invalid.
> {color:red}com.fasterxml.jackson.databind.exc.InvalidFormatException: Can not
> construct instance of int from String value '23a': not a valid Integer
> value{color}
> at [Source:
> {"uuid":"261e36cd-599e-4306-93b2-add0291de588","last_modified":1511520352482,"version":"2.3.0.20500","name":"DEFAULT.STREAMING_TABLE","clusters":[{"uuid":null,"last_modified":0,"version":"2.3.0.20500","brokers":[{"id":"23a","host":"1","port":1}],"newBroker":{"id":"23a","host":"1","port":1}}],"topic":"kafka
>
> topic","timeout":6,"parserName":"org.apache.kylin.source.kafka.TimedJsonStreamParser","timestampField":null,"margin":0,"parserProperties":"tsColName=datetime"};
> {panel}
> Then I find the server code, it also show the ID and Port must be integer, as
> follow:
> {code:java}
> public class BrokerConfig implements Serializable{
> @JsonProperty("id")
> private int id;
> ..
> @JsonProperty("port")
> private int port;
> {code}
> It means the parameter ID and Port are both not allowed for non-integer
> types, so we should solve them at the web page.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KYLIN-3058) We should limit the integer type ID and Port for "Kafka Setting" in "Streaming Cluster" page
[
https://issues.apache.org/jira/browse/KYLIN-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
peng.jianhua updated KYLIN-3058:
Attachment: kafka_setting(supplement).png
measures(supplement).png
advanced_setting(supplement).png
> We should limit the integer type ID and Port for "Kafka Setting" in
> "Streaming Cluster" page
>
>
> Key: KYLIN-3058
> URL: https://issues.apache.org/jira/browse/KYLIN-3058
> Project: Kylin
> Issue Type: Bug
> Components: Web
>Reporter: peng.jianhua
>Assignee: peng.jianhua
> Labels: patch
> Fix For: v2.3.0
>
> Attachments: advanced_setting(supplement).png,
> create_non_interger_ID.png, edit_non_interger_ID.png,
> kafka_setting(supplement).png, measures(supplement).png,
> streaming_table_dashboard.png
>
>
> When you create or edit one streaming table, then set a non-integer type ID
> for "Kafka Setting" in "Streaming Cluster" page( refer to
> [^streaming_table_dashboard.png]), at last save it, you will find an error
> message page will pop up.
> 1. Create a streaming table, then set a non-integer type ID to save, such as
> "23a", you will get the error message page, refer to
> [^create_non_interger_ID.png];
> 2. Edit a streaming table, then modify a non-integer type ID to save, such as
> "23a", you will also get another error message page, refer to
> [^edit_non_interger_ID.png];
> In order to find out the cause of the problem, I analyze the Kylin server
> log, then I find the error, as follow:
> {panel:title=Kylin server log}
> 2017-11-24 18:46:07,413 ERROR [http-bio-7070-exec-14]
> controller.StreamingController:280 : The data KafkaConfig definition is
> invalid.
> {color:red}com.fasterxml.jackson.databind.exc.InvalidFormatException: Can not
> construct instance of int from String value '23a': not a valid Integer
> value{color}
> at [Source:
> {"uuid":"261e36cd-599e-4306-93b2-add0291de588","last_modified":1511520352482,"version":"2.3.0.20500","name":"DEFAULT.STREAMING_TABLE","clusters":[{"uuid":null,"last_modified":0,"version":"2.3.0.20500","brokers":[{"id":"23a","host":"1","port":1}],"newBroker":{"id":"23a","host":"1","port":1}}],"topic":"kafka
>
> topic","timeout":6,"parserName":"org.apache.kylin.source.kafka.TimedJsonStreamParser","timestampField":null,"margin":0,"parserProperties":"tsColName=datetime"};
> {panel}
> Then I find the server code, it also show the ID and Port must be integer, as
> follow:
> {code:java}
> public class BrokerConfig implements Serializable{
> @JsonProperty("id")
> private int id;
> ..
> @JsonProperty("port")
> private int port;
> {code}
> It means the parameter ID and Port are both not allowed for non-integer
> types, so we should solve them at the web page.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KYLIN-3065) Add 'First' and 'Last' button in case 'Query History' is too much
[ https://issues.apache.org/jira/browse/KYLIN-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated KYLIN-3065: Description: When the 'Query History' or 'Saved Queries' is too much.Just 'Previous' and 'Next' can not meet the demand. Such as I just want to find my first query and I've searched too much times,I need to click to much times to find out. So I add some attributes for the label 'Pagination'. The following 01.png is the comparison picture. was: When the 'Query History' or 'Saved Queries' is too much.Just 'Previous' and 'Next' can not meet the demand. So I add some attributes for the label 'Pagination'. The following 01.png is the comparison picture. > Add 'First' and 'Last' button in case 'Query History' is too much > - > > Key: KYLIN-3065 > URL: https://issues.apache.org/jira/browse/KYLIN-3065 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Minor > Attachments: > 0001-KYLIN-3065-Add-First-and-Last-button-in-case-Query-H.patch, 01.png > > > When the 'Query History' or 'Saved Queries' is too much.Just 'Previous' and > 'Next' can not meet the demand. > Such as I just want to find my first query and I've searched too much times,I > need to click to much times to find out. > So I add some attributes for the label 'Pagination'. > The following 01.png is the comparison picture. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-3065) Add 'First' and 'Last' button in case 'Query History' is too much
[ https://issues.apache.org/jira/browse/KYLIN-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated KYLIN-3065: Attachment: 0001-KYLIN-3065-Add-First-and-Last-button-in-case-Query-H.patch > Add 'First' and 'Last' button in case 'Query History' is too much > - > > Key: KYLIN-3065 > URL: https://issues.apache.org/jira/browse/KYLIN-3065 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Minor > Attachments: > 0001-KYLIN-3065-Add-First-and-Last-button-in-case-Query-H.patch, 01.png > > > When the 'Query History' or 'Saved Queries' is too much.Just 'Previous' and > 'Next' can not meet the demand. > So I add some attributes for the label 'Pagination'. > The following 01.png is the comparison picture. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-3065) Add 'First' and 'Last' button in case 'Query History' is too much
[ https://issues.apache.org/jira/browse/KYLIN-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated KYLIN-3065: Attachment: 01.png > Add 'First' and 'Last' button in case 'Query History' is too much > - > > Key: KYLIN-3065 > URL: https://issues.apache.org/jira/browse/KYLIN-3065 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Minor > Attachments: 01.png > > > When the 'Query History' or 'Saved Queries' is too much.Just 'Previous' and > 'Next' can not meet the demand. > So I add some attributes for the label 'Pagination'. > The following 01.png is the comparison picture. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-3065) Add 'First' and 'Last' button in case 'Query History' is too much
peng.jianhua created KYLIN-3065: --- Summary: Add 'First' and 'Last' button in case 'Query History' is too much Key: KYLIN-3065 URL: https://issues.apache.org/jira/browse/KYLIN-3065 Project: Kylin Issue Type: Improvement Components: Web Reporter: peng.jianhua Assignee: peng.jianhua Priority: Minor When the 'Query History' or 'Saved Queries' is too much.Just 'Previous' and 'Next' can not meet the demand. So I add some attributes for the label 'Pagination'. The following 01.png is the comparison picture. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-3063) load-hive-conf.sh should not get the commented configuration item
[ https://issues.apache.org/jira/browse/KYLIN-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated KYLIN-3063: Attachment: 0001-KYLIN-3063-load-hive-conf.sh-should-not-get-the-comm.patch > load-hive-conf.sh should not get the commented configuration item > - > > Key: KYLIN-3063 > URL: https://issues.apache.org/jira/browse/KYLIN-3063 > Project: Kylin > Issue Type: Bug > Components: General >Affects Versions: v2.2.0 >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Minor > Attachments: > 0001-KYLIN-3063-load-hive-conf.sh-should-not-get-the-comm.patch > > > load-hive-conf.sh should not get the commented configuration item in > kylin_hive_conf.xml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2882) Disable datepicker input avoid user typing issue
[ https://issues.apache.org/jira/browse/KYLIN-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267934#comment-16267934 ] liyang commented on KYLIN-2882: --- Yeah, I prefer typing than pointing mouses. > Disable datepicker input avoid user typing issue > > > Key: KYLIN-2882 > URL: https://issues.apache.org/jira/browse/KYLIN-2882 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Pan, Julian >Assignee: Pan, Julian >Priority: Minor > > When user typing in input for datepicker, which will cause date error issue. > Could we add the attribute read-only for datepicker input? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-3064) Yarn timeline-service will start jersey client when submit mr job, remove it
[ https://issues.apache.org/jira/browse/KYLIN-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yiming.xu updated KYLIN-3064: - Summary: Yarn timeline-service will start jersey client when submit mr job, remove it (was: Yarn timeline-service will start jersey client, remove it) > Yarn timeline-service will start jersey client when submit mr job, remove it > > > Key: KYLIN-3064 > URL: https://issues.apache.org/jira/browse/KYLIN-3064 > Project: Kylin > Issue Type: Bug >Reporter: yiming.xu >Priority: Minor > > We not used timeline service, when the yarn.timeline-service.enabled is true, > yarn client will start a jersey client, it will use many resources. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-3064) Yarn timeline-service will start jersey client, remove it
yiming.xu created KYLIN-3064: Summary: Yarn timeline-service will start jersey client, remove it Key: KYLIN-3064 URL: https://issues.apache.org/jira/browse/KYLIN-3064 Project: Kylin Issue Type: Bug Reporter: yiming.xu Priority: Minor We not used timeline service, when the yarn.timeline-service.enabled is true, yarn client will start a jersey client, it will use many resources. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-3049) Filter the invalid zero value of "Auto Merge Thresholds" parameter when you create or upate a cube.
[ https://issues.apache.org/jira/browse/KYLIN-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266552#comment-16266552 ] peng.jianhua commented on KYLIN-3049: - hi [~Zhixiong Chen], thanks for your suggestion, I have updated the patch. 1. modify the $scope.prepareCube function 2. add the function 'removeElementInArrayByValue' in utils.js please check it, thanks! > Filter the invalid zero value of "Auto Merge Thresholds" parameter when you > create or upate a cube. > --- > > Key: KYLIN-3049 > URL: https://issues.apache.org/jira/browse/KYLIN-3049 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: peng.jianhua >Assignee: peng.jianhua > Labels: patch, scope > Fix For: v2.3.0 > > Attachments: > 0001-KYLIN-3049-Filter-the-invalid-zero-value-of-Auto-Mer.patch, > add_or_update_cube.png, show_cube.png > > > 1. Open the Model page; > 2. Create a new cube, click the "New Thresholds" button in the "Refresh > Setting" tab, and don't input any value( refer to [^add_or_update_cube.png]), > then complete the follow steps, at last save it; > 3. Choose the cube you just created, go to the "Refresh Setting" tab, you > will find the zero hours in "Auto Merge Thresholds" list, which is invalid > but saved in the server( refer to [^show_cube.png]); > 4. Similarly, update a existent cube, do the same steps, you will also find > the invalid zero value saved in the server. > As we know, the zero value of "Auto Merge Thresholds" parameter is invalid, > so we should filter it before sending it to server. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-3049) Filter the invalid zero value of "Auto Merge Thresholds" parameter when you create or upate a cube.
[ https://issues.apache.org/jira/browse/KYLIN-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated KYLIN-3049: Attachment: 0001-KYLIN-3049-Filter-the-invalid-zero-value-of-Auto-Mer.patch > Filter the invalid zero value of "Auto Merge Thresholds" parameter when you > create or upate a cube. > --- > > Key: KYLIN-3049 > URL: https://issues.apache.org/jira/browse/KYLIN-3049 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: peng.jianhua >Assignee: peng.jianhua > Labels: patch, scope > Fix For: v2.3.0 > > Attachments: > 0001-KYLIN-3049-Filter-the-invalid-zero-value-of-Auto-Mer.patch, > add_or_update_cube.png, show_cube.png > > > 1. Open the Model page; > 2. Create a new cube, click the "New Thresholds" button in the "Refresh > Setting" tab, and don't input any value( refer to [^add_or_update_cube.png]), > then complete the follow steps, at last save it; > 3. Choose the cube you just created, go to the "Refresh Setting" tab, you > will find the zero hours in "Auto Merge Thresholds" list, which is invalid > but saved in the server( refer to [^show_cube.png]); > 4. Similarly, update a existent cube, do the same steps, you will also find > the invalid zero value saved in the server. > As we know, the zero value of "Auto Merge Thresholds" parameter is invalid, > so we should filter it before sending it to server. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-3049) Filter the invalid zero value of "Auto Merge Thresholds" parameter when you create or upate a cube.
[ https://issues.apache.org/jira/browse/KYLIN-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated KYLIN-3049: Attachment: (was: 0001-KYLIN-3049-Filter-the-invalid-zero-value-of-Auto-Mer.patch) > Filter the invalid zero value of "Auto Merge Thresholds" parameter when you > create or upate a cube. > --- > > Key: KYLIN-3049 > URL: https://issues.apache.org/jira/browse/KYLIN-3049 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: peng.jianhua >Assignee: peng.jianhua > Labels: patch, scope > Fix For: v2.3.0 > > Attachments: > 0001-KYLIN-3049-Filter-the-invalid-zero-value-of-Auto-Mer.patch, > add_or_update_cube.png, show_cube.png > > > 1. Open the Model page; > 2. Create a new cube, click the "New Thresholds" button in the "Refresh > Setting" tab, and don't input any value( refer to [^add_or_update_cube.png]), > then complete the follow steps, at last save it; > 3. Choose the cube you just created, go to the "Refresh Setting" tab, you > will find the zero hours in "Auto Merge Thresholds" list, which is invalid > but saved in the server( refer to [^show_cube.png]); > 4. Similarly, update a existent cube, do the same steps, you will also find > the invalid zero value saved in the server. > As we know, the zero value of "Auto Merge Thresholds" parameter is invalid, > so we should filter it before sending it to server. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-1369) Display Build Time on Cube segment tabpage
[ https://issues.apache.org/jira/browse/KYLIN-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1369: - Summary: Display Build Time on Cube segment tabpage (was: Display LastBuildTime on Cube segment tabpage) > Display Build Time on Cube segment tabpage > -- > > Key: KYLIN-1369 > URL: https://issues.apache.org/jira/browse/KYLIN-1369 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Dong Li >Assignee: Dipesh >Priority: Minor > Labels: newbie > Attachments: Screen Shot 2016-02-22 at 4.18.34 PM.png > > > User may want to know when did the cube segment built, so he can do some > maintenance job. > Now we have the field in RestAPI JSON Result, one thing to do is to display > it on WebUI. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
