[jira] [Updated] (KYLIN-3460) {fn CURRENT_DATE()} parse error
[
https://issues.apache.org/jira/browse/KYLIN-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaofeng SHI updated KYLIN-3460:
Fix Version/s: v2.5.0
v2.4.1
> {fn CURRENT_DATE()} parse error
> ---
>
> Key: KYLIN-3460
> URL: https://issues.apache.org/jira/browse/KYLIN-3460
> Project: Kylin
> Issue Type: Bug
> Components: Driver - ODBC, Query Engine
>Affects Versions: v2.3.0, v2.3.1, v2.4.0
>Reporter: Temple Zhou
>Assignee: Temple Zhou
>Priority: Critical
> Fix For: v2.4.1, v2.5.0
>
>
> Dear all,
> I'm facing a very critical problem. When I use Tableau 10.5 with Kylin 2.1.0,
> the Tableau Server will send many SQL with "{fn CURRENT_DATE()}" via ODBC
> Driver(2.1.0), and the Kylin Server 2.1.0 will parse the CURRENT_DATE() to
> "2018-07-20 00:00:00"(the real current date). the logs are as below
> {noformat}
> Query Id: 14e7b152-6be0-4539-8fd0-c28bbffa6b25
> SQL: SELECT "APP_DAILY_ACTIVE_USER_PROPERTY_DI"."AV" AS "AV",
>COUNT(DISTINCT "APP_DAILY_ACTIVE_USER_PROPERTY_DI"."MC") AS
> "usr_Calculation_267682710052360192_ok"
> FROM "ADL"."APP_DAILY_ACTIVE_USER_PROPERTY_DI"
> "APP_DAILY_ACTIVE_USER_PROPERTY_DI"
> LEFT JOIN "DIM"."APP" "APP" ON ("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."AC" =
> "APP"."ID")
> INNER JOIN "DIM"."CALENDAR" "CALENDAR" ON
> ("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."ACTION_DT" = "CALENDAR"."CAL_DT")
> WHERE ((CAST("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."ACTION_DT" AS TIMESTAMP) >=
> {ts '2018-06-20 00:00:00'})
>AND (CAST("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."ACTION_DT" AS
> TIMESTAMP) < {ts '2018-07-20 00:00:00'})
>AND ("APP"."NAME" = 'xxx'))
> GROUP BY "APP_DAILY_ACTIVE_USER_PROPERTY_DI"."AV"
> User: ADMIN
> Success: true
> Duration: 0.06
> Project: app
> {noformat}
> However, recently, I upgrade my Kylin Server to 2.3.1 even 2.4.0, then there
> are many Tableau reports get the same error due to the SQL contain {fn
> CURRENT_DATE()}
> [Tableau Error
> Image|https://ws3.sinaimg.cn/large/006tKfTcgy1ftfbzshgs1j30fc0g2dhi.jpg]
> Besides, I found that the logs(2.3.1&2.4.0) are different from the
> logs(2.1.0), the logs(2.4.0) are as below
> {noformat}
> Query Id: b160f20c-84e4-4b81-bfe9-54ed22a723d6
> SQL: SELECT "APP_DAILY_ACTIVE_USER_PROPERTY_DI"."AV" AS "AV",
>COUNT(DISTINCT "APP_DAILY_ACTIVE_USER_PROPERTY_DI"."MC") AS
> "usr_Calculation_267682710052360192_ok"
> FROM "ADL"."APP_DAILY_ACTIVE_USER_PROPERTY_DI"
> "APP_DAILY_ACTIVE_USER_PROPERTY_DI"
> LEFT JOIN "DIM"."APP" "APP" ON ("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."AC" =
> "APP"."ID")
> INNER JOIN "DIM"."CALENDAR" "CALENDAR" ON
> ("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."ACTION_DT" = "CALENDAR"."CAL_DT")
> WHERE ((CAST("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."ACTION_DT" AS TIMESTAMP) >=
> {fn TIMESTAMPADD(SQL_TSI_DAY,-29,{fn CURRENT_DATE()})})
>AND (CAST("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."ACTION_DT" AS
> TIMESTAMP) < {fn TIMESTAMPADD(SQL_TSI_DAY,1,{fn CURRENT_DATE()})})
>AND ("APP"."NAME" = 'xxx')
>AND ("APP"."PLATFORM" = 'Android'))
> GROUP BY "APP_DAILY_ACTIVE_USER_PROPERTY_DI"."AV"
> User: ADMIN
> Success: false
> Duration: 0.029
> Project: app
> {noformat}
> The problem that bothers me the most is that why the older version can parse
> the "fn CURRENT_DATE()" but the newer can't. :( :( :(
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3460) {fn CURRENT_DATE()} parse error
[
https://issues.apache.org/jira/browse/KYLIN-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555097#comment-16555097
]
Shaofeng SHI commented on KYLIN-3460:
-
Hi Temple, thanks for the reporting, would you like to contribute a patch for
Kylin?
> {fn CURRENT_DATE()} parse error
> ---
>
> Key: KYLIN-3460
> URL: https://issues.apache.org/jira/browse/KYLIN-3460
> Project: Kylin
> Issue Type: Bug
> Components: Driver - ODBC, Query Engine
>Affects Versions: v2.3.0, v2.3.1, v2.4.0
>Reporter: Temple Zhou
>Assignee: Temple Zhou
>Priority: Critical
> Fix For: v2.4.1, v2.5.0
>
>
> Dear all,
> I'm facing a very critical problem. When I use Tableau 10.5 with Kylin 2.1.0,
> the Tableau Server will send many SQL with "{fn CURRENT_DATE()}" via ODBC
> Driver(2.1.0), and the Kylin Server 2.1.0 will parse the CURRENT_DATE() to
> "2018-07-20 00:00:00"(the real current date). the logs are as below
> {noformat}
> Query Id: 14e7b152-6be0-4539-8fd0-c28bbffa6b25
> SQL: SELECT "APP_DAILY_ACTIVE_USER_PROPERTY_DI"."AV" AS "AV",
>COUNT(DISTINCT "APP_DAILY_ACTIVE_USER_PROPERTY_DI"."MC") AS
> "usr_Calculation_267682710052360192_ok"
> FROM "ADL"."APP_DAILY_ACTIVE_USER_PROPERTY_DI"
> "APP_DAILY_ACTIVE_USER_PROPERTY_DI"
> LEFT JOIN "DIM"."APP" "APP" ON ("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."AC" =
> "APP"."ID")
> INNER JOIN "DIM"."CALENDAR" "CALENDAR" ON
> ("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."ACTION_DT" = "CALENDAR"."CAL_DT")
> WHERE ((CAST("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."ACTION_DT" AS TIMESTAMP) >=
> {ts '2018-06-20 00:00:00'})
>AND (CAST("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."ACTION_DT" AS
> TIMESTAMP) < {ts '2018-07-20 00:00:00'})
>AND ("APP"."NAME" = 'xxx'))
> GROUP BY "APP_DAILY_ACTIVE_USER_PROPERTY_DI"."AV"
> User: ADMIN
> Success: true
> Duration: 0.06
> Project: app
> {noformat}
> However, recently, I upgrade my Kylin Server to 2.3.1 even 2.4.0, then there
> are many Tableau reports get the same error due to the SQL contain {fn
> CURRENT_DATE()}
> [Tableau Error
> Image|https://ws3.sinaimg.cn/large/006tKfTcgy1ftfbzshgs1j30fc0g2dhi.jpg]
> Besides, I found that the logs(2.3.1&2.4.0) are different from the
> logs(2.1.0), the logs(2.4.0) are as below
> {noformat}
> Query Id: b160f20c-84e4-4b81-bfe9-54ed22a723d6
> SQL: SELECT "APP_DAILY_ACTIVE_USER_PROPERTY_DI"."AV" AS "AV",
>COUNT(DISTINCT "APP_DAILY_ACTIVE_USER_PROPERTY_DI"."MC") AS
> "usr_Calculation_267682710052360192_ok"
> FROM "ADL"."APP_DAILY_ACTIVE_USER_PROPERTY_DI"
> "APP_DAILY_ACTIVE_USER_PROPERTY_DI"
> LEFT JOIN "DIM"."APP" "APP" ON ("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."AC" =
> "APP"."ID")
> INNER JOIN "DIM"."CALENDAR" "CALENDAR" ON
> ("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."ACTION_DT" = "CALENDAR"."CAL_DT")
> WHERE ((CAST("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."ACTION_DT" AS TIMESTAMP) >=
> {fn TIMESTAMPADD(SQL_TSI_DAY,-29,{fn CURRENT_DATE()})})
>AND (CAST("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."ACTION_DT" AS
> TIMESTAMP) < {fn TIMESTAMPADD(SQL_TSI_DAY,1,{fn CURRENT_DATE()})})
>AND ("APP"."NAME" = 'xxx')
>AND ("APP"."PLATFORM" = 'Android'))
> GROUP BY "APP_DAILY_ACTIVE_USER_PROPERTY_DI"."AV"
> User: ADMIN
> Success: false
> Duration: 0.029
> Project: app
> {noformat}
> The problem that bothers me the most is that why the older version can parse
> the "fn CURRENT_DATE()" but the newer can't. :( :( :(
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KYLIN-3460) {fn CURRENT_DATE()} parse error
[
https://issues.apache.org/jira/browse/KYLIN-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaofeng SHI updated KYLIN-3460:
Priority: Major (was: Critical)
> {fn CURRENT_DATE()} parse error
> ---
>
> Key: KYLIN-3460
> URL: https://issues.apache.org/jira/browse/KYLIN-3460
> Project: Kylin
> Issue Type: Bug
> Components: Driver - ODBC, Query Engine
>Affects Versions: v2.3.0, v2.3.1, v2.4.0
>Reporter: Temple Zhou
>Assignee: Temple Zhou
>Priority: Major
> Fix For: v2.4.1, v2.5.0
>
>
> Dear all,
> I'm facing a very critical problem. When I use Tableau 10.5 with Kylin 2.1.0,
> the Tableau Server will send many SQL with "{fn CURRENT_DATE()}" via ODBC
> Driver(2.1.0), and the Kylin Server 2.1.0 will parse the CURRENT_DATE() to
> "2018-07-20 00:00:00"(the real current date). the logs are as below
> {noformat}
> Query Id: 14e7b152-6be0-4539-8fd0-c28bbffa6b25
> SQL: SELECT "APP_DAILY_ACTIVE_USER_PROPERTY_DI"."AV" AS "AV",
>COUNT(DISTINCT "APP_DAILY_ACTIVE_USER_PROPERTY_DI"."MC") AS
> "usr_Calculation_267682710052360192_ok"
> FROM "ADL"."APP_DAILY_ACTIVE_USER_PROPERTY_DI"
> "APP_DAILY_ACTIVE_USER_PROPERTY_DI"
> LEFT JOIN "DIM"."APP" "APP" ON ("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."AC" =
> "APP"."ID")
> INNER JOIN "DIM"."CALENDAR" "CALENDAR" ON
> ("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."ACTION_DT" = "CALENDAR"."CAL_DT")
> WHERE ((CAST("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."ACTION_DT" AS TIMESTAMP) >=
> {ts '2018-06-20 00:00:00'})
>AND (CAST("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."ACTION_DT" AS
> TIMESTAMP) < {ts '2018-07-20 00:00:00'})
>AND ("APP"."NAME" = 'xxx'))
> GROUP BY "APP_DAILY_ACTIVE_USER_PROPERTY_DI"."AV"
> User: ADMIN
> Success: true
> Duration: 0.06
> Project: app
> {noformat}
> However, recently, I upgrade my Kylin Server to 2.3.1 even 2.4.0, then there
> are many Tableau reports get the same error due to the SQL contain {fn
> CURRENT_DATE()}
> [Tableau Error
> Image|https://ws3.sinaimg.cn/large/006tKfTcgy1ftfbzshgs1j30fc0g2dhi.jpg]
> Besides, I found that the logs(2.3.1&2.4.0) are different from the
> logs(2.1.0), the logs(2.4.0) are as below
> {noformat}
> Query Id: b160f20c-84e4-4b81-bfe9-54ed22a723d6
> SQL: SELECT "APP_DAILY_ACTIVE_USER_PROPERTY_DI"."AV" AS "AV",
>COUNT(DISTINCT "APP_DAILY_ACTIVE_USER_PROPERTY_DI"."MC") AS
> "usr_Calculation_267682710052360192_ok"
> FROM "ADL"."APP_DAILY_ACTIVE_USER_PROPERTY_DI"
> "APP_DAILY_ACTIVE_USER_PROPERTY_DI"
> LEFT JOIN "DIM"."APP" "APP" ON ("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."AC" =
> "APP"."ID")
> INNER JOIN "DIM"."CALENDAR" "CALENDAR" ON
> ("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."ACTION_DT" = "CALENDAR"."CAL_DT")
> WHERE ((CAST("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."ACTION_DT" AS TIMESTAMP) >=
> {fn TIMESTAMPADD(SQL_TSI_DAY,-29,{fn CURRENT_DATE()})})
>AND (CAST("APP_DAILY_ACTIVE_USER_PROPERTY_DI"."ACTION_DT" AS
> TIMESTAMP) < {fn TIMESTAMPADD(SQL_TSI_DAY,1,{fn CURRENT_DATE()})})
>AND ("APP"."NAME" = 'xxx')
>AND ("APP"."PLATFORM" = 'Android'))
> GROUP BY "APP_DAILY_ACTIVE_USER_PROPERTY_DI"."AV"
> User: ADMIN
> Success: false
> Duration: 0.029
> Project: app
> {noformat}
> The problem that bothers me the most is that why the older version can parse
> the "fn CURRENT_DATE()" but the newer can't. :( :( :(
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3418) User interface for hybrid model
[
https://issues.apache.org/jira/browse/KYLIN-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555075#comment-16555075
]
ASF GitHub Bot commented on KYLIN-3418:
---
shaofengshi commented on a change in pull request #173: KYLIN-3418 User
interface for hybrid model - Frontend
URL: https://github.com/apache/kylin/pull/173#discussion_r204969762
##
File path: webapp/app/js/model/hybridCubeManager.js
##
@@ -0,0 +1,60 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+*/
+
+KylinApp.service('hybridCubeManager', function($q, HybridCubeService,
ProjectModel) {
+ var _this = this;
+ this.hybridCubes = [];
Review comment:
Hi, there is no "hybridCubes" concept, please use "hybridInstance"
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> User interface for hybrid model
> ---
>
> Key: KYLIN-3418
> URL: https://issues.apache.org/jira/browse/KYLIN-3418
> Project: Kylin
> Issue Type: Improvement
> Components: Web
>Reporter: Shaofeng SHI
>Assignee: Roger
>Priority: Major
> Fix For: v2.5.0
>
>
> Hybrid model is useful for model change. While now there is no entry for it
> from GUI, this makes many users don't see such feature.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3418) User interface for hybrid model
[
https://issues.apache.org/jira/browse/KYLIN-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555070#comment-16555070
]
ASF GitHub Bot commented on KYLIN-3418:
---
shaofengshi commented on a change in pull request #174: KYLIN-3418 adjust
hybrid API
URL: https://github.com/apache/kylin/pull/174#discussion_r204969453
##
File path:
server-base/src/main/java/org/apache/kylin/rest/service/HybridService.java
##
@@ -66,8 +66,7 @@ public HybridInstance createHybridCube(String hybridName,
String projectName, St
return getHybridInstance(hybridName);
}
-public HybridInstance updateHybridCube(String hybridName, String
projectName, String modelName,
-String[] cubeNames) {
+public HybridRespone updateHybridCube(String hybridName, String
projectName, String modelName, String[] cubeNames) {
Review comment:
"HybridInstance" is a better name than "HybridCube"
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> User interface for hybrid model
> ---
>
> Key: KYLIN-3418
> URL: https://issues.apache.org/jira/browse/KYLIN-3418
> Project: Kylin
> Issue Type: Improvement
> Components: Web
>Reporter: Shaofeng SHI
>Assignee: Roger
>Priority: Major
> Fix For: v2.5.0
>
>
> Hybrid model is useful for model change. While now there is no entry for it
> from GUI, this makes many users don't see such feature.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3418) User interface for hybrid model
[
https://issues.apache.org/jira/browse/KYLIN-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555037#comment-16555037
]
ASF GitHub Bot commented on KYLIN-3418:
---
shaofengshi commented on a change in pull request #174: KYLIN-3418 adjust
hybrid API
URL: https://github.com/apache/kylin/pull/174#discussion_r204966171
##
File path:
server-base/src/main/java/org/apache/kylin/rest/service/HybridService.java
##
@@ -43,8 +44,7 @@
@Autowired
private AclEvaluate aclEvaluate;
-public HybridInstance createHybridCube(String hybridName, String
projectName, String modelName,
-String[] cubeNames) {
+public HybridRespone createHybridCube(String hybridName, String
projectName, String modelName, String[] cubeNames) {
Review comment:
"HybridRespone" is from the rest layer, it shouldn't be referenced at the
service layer. Here the interface should be "HybridInstance"
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> User interface for hybrid model
> ---
>
> Key: KYLIN-3418
> URL: https://issues.apache.org/jira/browse/KYLIN-3418
> Project: Kylin
> Issue Type: Improvement
> Components: Web
>Reporter: Shaofeng SHI
>Assignee: Roger
>Priority: Major
> Fix For: v2.5.0
>
>
> Hybrid model is useful for model change. While now there is no entry for it
> from GUI, this makes many users don't see such feature.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3418) User interface for hybrid model
[
https://issues.apache.org/jira/browse/KYLIN-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555035#comment-16555035
]
ASF GitHub Bot commented on KYLIN-3418:
---
shaofengshi commented on a change in pull request #174: KYLIN-3418 adjust
hybrid API
URL: https://github.com/apache/kylin/pull/174#discussion_r204965852
##
File path:
server-base/src/main/java/org/apache/kylin/rest/job/HybridCubeCLI.java
##
@@ -105,6 +105,18 @@ protected void execute(OptionsHelper optionsHelper)
throws Exception {
String projectName = optionsHelper.getOptionValue(OPTION_PROJECT);
String modelName = optionsHelper.getOptionValue(OPTION_MODEL);
String cubeNamesStr = optionsHelper.getOptionValue(OPTION_CUBES);
+
+HybridInstance hybridInstance =
hybridManager.getHybridInstance(hybridName);
+
+if ("delete".equals(action)) {
+if (hybridInstance == null) {
+throw new RuntimeException("The Hybrid Cube doesn't exist,
could not delete: " + hybridName);
Review comment:
Please use illegal argument exception.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> User interface for hybrid model
> ---
>
> Key: KYLIN-3418
> URL: https://issues.apache.org/jira/browse/KYLIN-3418
> Project: Kylin
> Issue Type: Improvement
> Components: Web
>Reporter: Shaofeng SHI
>Assignee: Roger
>Priority: Major
> Fix For: v2.5.0
>
>
> Hybrid model is useful for model change. While now there is no entry for it
> from GUI, this makes many users don't see such feature.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3418) User interface for hybrid model
[ https://issues.apache.org/jira/browse/KYLIN-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16554319#comment-16554319 ] ASF GitHub Bot commented on KYLIN-3418: --- asfgit commented on issue #174: KYLIN-3418 adjust hybrid API URL: https://github.com/apache/kylin/pull/174#issuecomment-407431944 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > User interface for hybrid model > --- > > Key: KYLIN-3418 > URL: https://issues.apache.org/jira/browse/KYLIN-3418 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Shaofeng SHI >Assignee: Roger >Priority: Major > Fix For: v2.5.0 > > > Hybrid model is useful for model change. While now there is no entry for it > from GUI, this makes many users don't see such feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3418) User interface for hybrid model
[ https://issues.apache.org/jira/browse/KYLIN-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16554318#comment-16554318 ] ASF GitHub Bot commented on KYLIN-3418: --- Wayne1c opened a new pull request #174: KYLIN-3418 adjust hybrid API URL: https://github.com/apache/kylin/pull/174 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > User interface for hybrid model > --- > > Key: KYLIN-3418 > URL: https://issues.apache.org/jira/browse/KYLIN-3418 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Shaofeng SHI >Assignee: Roger >Priority: Major > Fix For: v2.5.0 > > > Hybrid model is useful for model change. While now there is no entry for it > from GUI, this makes many users don't see such feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3259) When a cube is deleted, remove it from the hybrid cube definition
[ https://issues.apache.org/jira/browse/KYLIN-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16554113#comment-16554113 ] Chao Long commented on KYLIN-3259: -- Hi [~liukaige], are you working on this? I would like to contribute a patch.:) > When a cube is deleted, remove it from the hybrid cube definition > - > > Key: KYLIN-3259 > URL: https://issues.apache.org/jira/browse/KYLIN-3259 > Project: Kylin > Issue Type: Improvement > Components: Metadata >Affects Versions: v2.2.0 > Environment: HDP 2.5.6, Kylin 2.2 >Reporter: Vsevolod Ostapenko >Assignee: Kaige Liu >Priority: Major > Fix For: v2.5.0 > > > When a cube is deleted, its references are not automatically removed from > existing hybrid cube definition. That can lead to errors down the road, if > user (or application) retrieves the list of cubes via REST API call and later > tries to update the hybrid cube. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3418) User interface for hybrid model
[ https://issues.apache.org/jira/browse/KYLIN-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16554104#comment-16554104 ] Chao Long commented on KYLIN-3418: -- Hi [~emiya0306], I`d like to support this issue on the API side. > User interface for hybrid model > --- > > Key: KYLIN-3418 > URL: https://issues.apache.org/jira/browse/KYLIN-3418 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Shaofeng SHI >Assignee: Roger >Priority: Major > Fix For: v2.5.0 > > > Hybrid model is useful for model change. While now there is no entry for it > from GUI, this makes many users don't see such feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KYLIN-3466) Should disable speculative mappers for those mapper only jobs
[ https://issues.apache.org/jira/browse/KYLIN-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong Yanghong resolved KYLIN-3466. --- Resolution: Not A Problem > Should disable speculative mappers for those mapper only jobs > - > > Key: KYLIN-3466 > URL: https://issues.apache.org/jira/browse/KYLIN-3466 > Project: Kylin > Issue Type: Improvement > Components: Job Engine >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong >Priority: Critical > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3466) Should disable speculative mappers for those mapper only jobs
[ https://issues.apache.org/jira/browse/KYLIN-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16554060#comment-16554060 ] Zhong Yanghong commented on KYLIN-3466: --- If using normal writer of output format, this issue may not happen and it's better to enable speculative. > Should disable speculative mappers for those mapper only jobs > - > > Key: KYLIN-3466 > URL: https://issues.apache.org/jira/browse/KYLIN-3466 > Project: Kylin > Issue Type: Improvement > Components: Job Engine >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong >Priority: Critical > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (KYLIN-3453) Improve cube size estimation for TOPN, COUNT DISTINCT
[ https://issues.apache.org/jira/browse/KYLIN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16553990#comment-16553990 ] Chao Long edited comment on KYLIN-3453 at 7/24/18 10:11 AM: I have done some tests on the enhancement, and the results are as belows： 1, test sample cube cube real size: !image-2018-07-24-16-30-50-804.png! before enhancement !image-2018-07-24-16-33-43-231.png! after enhancement !image-2018-07-24-16-29-07-359.png! 2，ssb dataSet cube real size !image-2018-07-24-16-37-09-199.png! before enhancement !image-2018-07-24-17-11-27-829.png! after enhancement !image-2018-07-24-17-12-25-880.png! And we can find that the estimatation of Cube size is more accurate after enhancement. was (Author: wayne0101): After the enhancement, I did some tests. 1, test sample cube cube real size: !image-2018-07-24-16-30-50-804.png! before enhancement !image-2018-07-24-16-33-43-231.png! after enhancement !image-2018-07-24-16-29-07-359.png! 2，ssb dataSet cube real size !image-2018-07-24-16-37-09-199.png! before enhancement !image-2018-07-24-17-11-27-829.png! after enhancement !image-2018-07-24-17-12-25-880.png! from the test result, we can find that after the enhancement, the estimates of cube size are more accurate. > Improve cube size estimation for TOPN, COUNT DISTINCT > - > > Key: KYLIN-3453 > URL: https://issues.apache.org/jira/browse/KYLIN-3453 > Project: Kylin > Issue Type: Improvement >Reporter: Chao Long >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > Attachments: image-2018-07-24-16-29-07-359.png, > image-2018-07-24-16-30-50-804.png, image-2018-07-24-16-33-43-231.png, > image-2018-07-24-16-37-09-199.png, image-2018-07-24-17-11-26-283.png, > image-2018-07-24-17-11-27-829.png, image-2018-07-24-17-12-25-880.png > > > Currently, Kylin has poor cube size estimation for TOPN, COUNT DISTINCT. We > should improve it, then we can get a reasonable split num when cube building. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3466) Should disable speculative mappers for those mapper only jobs
Zhong Yanghong created KYLIN-3466: - Summary: Should disable speculative mappers for those mapper only jobs Key: KYLIN-3466 URL: https://issues.apache.org/jira/browse/KYLIN-3466 Project: Kylin Issue Type: Improvement Components: Job Engine Reporter: Zhong Yanghong Assignee: Zhong Yanghong -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3453) Improve cube size estimation for TOPN, COUNT DISTINCT
[ https://issues.apache.org/jira/browse/KYLIN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16553990#comment-16553990 ] Chao Long commented on KYLIN-3453: -- After the enhancement, I did some tests. 1, test sample cube cube real size: !image-2018-07-24-16-30-50-804.png! before enhancement !image-2018-07-24-16-33-43-231.png! after enhancement !image-2018-07-24-16-29-07-359.png! 2，ssb dataSet cube real size !image-2018-07-24-16-37-09-199.png! before enhancement !image-2018-07-24-17-11-27-829.png! after enhancement !image-2018-07-24-17-12-25-880.png! from the test result, we can find that after the enhancement, the estimates of cube size are more accurate. > Improve cube size estimation for TOPN, COUNT DISTINCT > - > > Key: KYLIN-3453 > URL: https://issues.apache.org/jira/browse/KYLIN-3453 > Project: Kylin > Issue Type: Improvement >Reporter: Chao Long >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > Attachments: image-2018-07-24-16-29-07-359.png, > image-2018-07-24-16-30-50-804.png, image-2018-07-24-16-33-43-231.png, > image-2018-07-24-16-37-09-199.png, image-2018-07-24-17-11-26-283.png, > image-2018-07-24-17-11-27-829.png, image-2018-07-24-17-12-25-880.png > > > Currently, Kylin has poor cube size estimation for TOPN, COUNT DISTINCT. We > should improve it, then we can get a reasonable split num when cube building. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3453) Improve cube size estimation for TOPN, COUNT DISTINCT
[ https://issues.apache.org/jira/browse/KYLIN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Long updated KYLIN-3453: - Attachment: image-2018-07-24-17-12-25-880.png > Improve cube size estimation for TOPN, COUNT DISTINCT > - > > Key: KYLIN-3453 > URL: https://issues.apache.org/jira/browse/KYLIN-3453 > Project: Kylin > Issue Type: Improvement >Reporter: Chao Long >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > Attachments: image-2018-07-24-16-29-07-359.png, > image-2018-07-24-16-30-50-804.png, image-2018-07-24-16-33-43-231.png, > image-2018-07-24-16-37-09-199.png, image-2018-07-24-17-11-26-283.png, > image-2018-07-24-17-11-27-829.png, image-2018-07-24-17-12-25-880.png > > > Currently, Kylin has poor cube size estimation for TOPN, COUNT DISTINCT. We > should improve it, then we can get a reasonable split num when cube building. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3453) Improve cube size estimation for TOPN, COUNT DISTINCT
[ https://issues.apache.org/jira/browse/KYLIN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Long updated KYLIN-3453: - Attachment: image-2018-07-24-17-11-26-283.png > Improve cube size estimation for TOPN, COUNT DISTINCT > - > > Key: KYLIN-3453 > URL: https://issues.apache.org/jira/browse/KYLIN-3453 > Project: Kylin > Issue Type: Improvement >Reporter: Chao Long >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > Attachments: image-2018-07-24-16-29-07-359.png, > image-2018-07-24-16-30-50-804.png, image-2018-07-24-16-33-43-231.png, > image-2018-07-24-16-37-09-199.png, image-2018-07-24-17-11-26-283.png, > image-2018-07-24-17-11-27-829.png > > > Currently, Kylin has poor cube size estimation for TOPN, COUNT DISTINCT. We > should improve it, then we can get a reasonable split num when cube building. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3453) Improve cube size estimation for TOPN, COUNT DISTINCT
[ https://issues.apache.org/jira/browse/KYLIN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Long updated KYLIN-3453: - Attachment: image-2018-07-24-17-11-27-829.png > Improve cube size estimation for TOPN, COUNT DISTINCT > - > > Key: KYLIN-3453 > URL: https://issues.apache.org/jira/browse/KYLIN-3453 > Project: Kylin > Issue Type: Improvement >Reporter: Chao Long >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > Attachments: image-2018-07-24-16-29-07-359.png, > image-2018-07-24-16-30-50-804.png, image-2018-07-24-16-33-43-231.png, > image-2018-07-24-16-37-09-199.png, image-2018-07-24-17-11-26-283.png, > image-2018-07-24-17-11-27-829.png > > > Currently, Kylin has poor cube size estimation for TOPN, COUNT DISTINCT. We > should improve it, then we can get a reasonable split num when cube building. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3453) Improve cube size estimation for TOPN, COUNT DISTINCT
[ https://issues.apache.org/jira/browse/KYLIN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Long updated KYLIN-3453: - Attachment: image-2018-07-24-16-37-09-199.png > Improve cube size estimation for TOPN, COUNT DISTINCT > - > > Key: KYLIN-3453 > URL: https://issues.apache.org/jira/browse/KYLIN-3453 > Project: Kylin > Issue Type: Improvement >Reporter: Chao Long >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > Attachments: image-2018-07-24-16-29-07-359.png, > image-2018-07-24-16-30-50-804.png, image-2018-07-24-16-33-43-231.png, > image-2018-07-24-16-37-09-199.png > > > Currently, Kylin has poor cube size estimation for TOPN, COUNT DISTINCT. We > should improve it, then we can get a reasonable split num when cube building. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3453) Improve cube size estimation for TOPN, COUNT DISTINCT
[ https://issues.apache.org/jira/browse/KYLIN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Long updated KYLIN-3453: - Attachment: image-2018-07-24-16-33-43-231.png > Improve cube size estimation for TOPN, COUNT DISTINCT > - > > Key: KYLIN-3453 > URL: https://issues.apache.org/jira/browse/KYLIN-3453 > Project: Kylin > Issue Type: Improvement >Reporter: Chao Long >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > Attachments: image-2018-07-24-16-29-07-359.png, > image-2018-07-24-16-30-50-804.png, image-2018-07-24-16-33-43-231.png > > > Currently, Kylin has poor cube size estimation for TOPN, COUNT DISTINCT. We > should improve it, then we can get a reasonable split num when cube building. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3453) Improve cube size estimation for TOPN, COUNT DISTINCT
[ https://issues.apache.org/jira/browse/KYLIN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Long updated KYLIN-3453: - Attachment: (was: image-2018-07-24-16-30-11-726.png) > Improve cube size estimation for TOPN, COUNT DISTINCT > - > > Key: KYLIN-3453 > URL: https://issues.apache.org/jira/browse/KYLIN-3453 > Project: Kylin > Issue Type: Improvement >Reporter: Chao Long >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > Attachments: image-2018-07-24-16-29-07-359.png, > image-2018-07-24-16-30-50-804.png > > > Currently, Kylin has poor cube size estimation for TOPN, COUNT DISTINCT. We > should improve it, then we can get a reasonable split num when cube building. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3453) Improve cube size estimation for TOPN, COUNT DISTINCT
[ https://issues.apache.org/jira/browse/KYLIN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Long updated KYLIN-3453: - Attachment: image-2018-07-24-16-30-50-804.png > Improve cube size estimation for TOPN, COUNT DISTINCT > - > > Key: KYLIN-3453 > URL: https://issues.apache.org/jira/browse/KYLIN-3453 > Project: Kylin > Issue Type: Improvement >Reporter: Chao Long >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > Attachments: image-2018-07-24-16-29-07-359.png, > image-2018-07-24-16-30-50-804.png > > > Currently, Kylin has poor cube size estimation for TOPN, COUNT DISTINCT. We > should improve it, then we can get a reasonable split num when cube building. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3453) Improve cube size estimation for TOPN, COUNT DISTINCT
[ https://issues.apache.org/jira/browse/KYLIN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Long updated KYLIN-3453: - Attachment: image-2018-07-24-16-30-11-726.png > Improve cube size estimation for TOPN, COUNT DISTINCT > - > > Key: KYLIN-3453 > URL: https://issues.apache.org/jira/browse/KYLIN-3453 > Project: Kylin > Issue Type: Improvement >Reporter: Chao Long >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > Attachments: image-2018-07-24-16-29-07-359.png, > image-2018-07-24-16-30-50-804.png > > > Currently, Kylin has poor cube size estimation for TOPN, COUNT DISTINCT. We > should improve it, then we can get a reasonable split num when cube building. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3453) Improve cube size estimation for TOPN, COUNT DISTINCT
[ https://issues.apache.org/jira/browse/KYLIN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Long updated KYLIN-3453: - Attachment: (was: image-2018-07-24-16-26-02-802.png) > Improve cube size estimation for TOPN, COUNT DISTINCT > - > > Key: KYLIN-3453 > URL: https://issues.apache.org/jira/browse/KYLIN-3453 > Project: Kylin > Issue Type: Improvement >Reporter: Chao Long >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > > Currently, Kylin has poor cube size estimation for TOPN, COUNT DISTINCT. We > should improve it, then we can get a reasonable split num when cube building. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3453) Improve cube size estimation for TOPN, COUNT DISTINCT
[ https://issues.apache.org/jira/browse/KYLIN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Long updated KYLIN-3453: - Attachment: image-2018-07-24-16-26-02-802.png > Improve cube size estimation for TOPN, COUNT DISTINCT > - > > Key: KYLIN-3453 > URL: https://issues.apache.org/jira/browse/KYLIN-3453 > Project: Kylin > Issue Type: Improvement >Reporter: Chao Long >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > > Currently, Kylin has poor cube size estimation for TOPN, COUNT DISTINCT. We > should improve it, then we can get a reasonable split num when cube building. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3453) Improve cube size estimation for TOPN, COUNT DISTINCT
[ https://issues.apache.org/jira/browse/KYLIN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Long updated KYLIN-3453: - Attachment: image-2018-07-24-16-26-46-907.png > Improve cube size estimation for TOPN, COUNT DISTINCT > - > > Key: KYLIN-3453 > URL: https://issues.apache.org/jira/browse/KYLIN-3453 > Project: Kylin > Issue Type: Improvement >Reporter: Chao Long >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > > Currently, Kylin has poor cube size estimation for TOPN, COUNT DISTINCT. We > should improve it, then we can get a reasonable split num when cube building. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (KYLIN-3465) kylin Kafka stream incremental build error
[
https://issues.apache.org/jira/browse/KYLIN-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenwen closed KYLIN-3465.
--
Resolution: Won't Do
I solved the problem by modifying the file.
# Kylin.properties
kylin.server.mode=job
kylin.server.cluster-servers=99.48.1.1:7070,99.48.1.2:7070,99.48.1.3:7070
kylin.server.mode=query
kylin.server.cluster-servers=99.48.1.1:7070,99.48.1.2:7070,99.48.1.3:7070
kylin.server.mode=query
kylin.server.cluster-servers=99.48.1.1:7070,99.48.1.2:7070,99.48.1.3:7070
> kylin Kafka stream incremental build error
> ---
>
> Key: KYLIN-3465
> URL: https://issues.apache.org/jira/browse/KYLIN-3465
> Project: Kylin
> Issue Type: Bug
> Components: Environment , Streaming
>Affects Versions: v2.4.0
>Reporter: chenwen
>Priority: Major
> Attachments: image-2018-07-24-14-34-38-102.png
>
>
> h1. Development environment:
> * Centos 7
> * Hadoop 2.7.2
> * Hbase 1.2.5
> * Hive 1.2.2
> * Kylin-2.4.0-bin-hbase1x
> * Kafka 0.10.2.2
> I built a cluster consisting of three machines that build the cube from the
> Kafka stream, but each time a new incremental build is made, the following
> error is displayed.
>
> {{2018-07-24 14:27:09,269 WARN [Scheduler 268704591 Job
> faf6db81-bc76-4b25-b838-8ca993e889d5-602] config.KafkaConsumerProperties:142
> : KYLIN_CONF property was not set, will seek KYLIN_HOME env variable
> 2018-07-24 14:27:09,295 ERROR [Scheduler 268704591 Job
> faf6db81-bc76-4b25-b838-8ca993e889d5-602] hadoop.KafkaFlatTableJob:131 :
> error in KafkaFlatTableJob java.lang.NullPointerException at
> org.apache.kylin.source.kafka.hadoop.KafkaFlatTableJob.setupMapper(KafkaFlatTableJob.java:143)
> at
> org.apache.kylin.source.kafka.hadoop.KafkaFlatTableJob.run(KafkaFlatTableJob.java:118)
> at
> org.apache.kylin.engine.mr.common.MapReduceExecutable.doWork(MapReduceExecutable.java:131)
> at
> org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:162)
> at
> org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:69)
> at
> org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:162)
> at
> org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:307)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745) 2018-07-24 14:27:09,296 ERROR
> [Scheduler 268704591 Job faf6db81-bc76-4b25-b838-8ca993e889d5-602]
> common.MapReduceExecutable:138 : error execute
> MapReduceExecutable\{id=faf6db81-bc76-4b25-b838-8ca993e889d5-00, name=Save
> data from Kafka, state=RUNNING} java.lang.NullPointerException at
> org.apache.kylin.source.kafka.hadoop.KafkaFlatTableJob.setupMapper(KafkaFlatTableJob.java:143)
> at
> org.apache.kylin.source.kafka.hadoop.KafkaFlatTableJob.run(KafkaFlatTableJob.java:118)
> at
> org.apache.kylin.engine.mr.common.MapReduceExecutable.doWork(MapReduceExecutable.java:131)
> at
> org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:162)
> at
> org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:69)
> at
> org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:162)
> at
> org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:307)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745) 2018-07-24 14:27:09,302 INFO
> [Scheduler 268704591 Job faf6db81-bc76-4b25-b838-8ca993e889d5-602]
> execution.ExecutableManager:411 : job
> id:faf6db81-bc76-4b25-b838-8ca993e889d5-00 from RUNNING to ERROR 2018-07-24
> 14:27:09,310 INFO [Scheduler 268704591 Job
> faf6db81-bc76-4b25-b838-8ca993e889d5-602] execution.ExecutableManager:411 :
> job id:faf6db81-bc76-4b25-b838-8ca993e889d5 from RUNNING to ERROR 2018-07-24
> 14:27:09,310 DEBUG [Scheduler 268704591 Job
> faf6db81-bc76-4b25-b838-8ca993e889d5-602] execution.AbstractExecutable:310 :
> no need to send email, user list is empty }}
> My current solution is to re-start the service of the job node every time,
> and build the incremental build again.
> h1. Kylin.properties
> kylin.server.mode=job
> kylin.server.cluster-servers=99.48.1.2:7070,99.48.1.3:7070
> kylin.server.mode=query
> kylin.server.cluster-servers=99.48.1.2:7070,99.48.1.3:7070
> kylin.server.mode=query
> kylin.server.cluster-servers=99.48.1.2:7070,99.48.1.3:7070
> 99.48.1.1:7070 job
> 99.48.1.2:7070 query
> 99.48.1.3:7070 query
> Thanks
--
This message
[jira] [Updated] (KYLIN-3453) Improve cube size estimation for TOPN, COUNT DISTINCT
[ https://issues.apache.org/jira/browse/KYLIN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Long updated KYLIN-3453: - Attachment: (was: image-2018-07-24-15-56-01-150.png) > Improve cube size estimation for TOPN, COUNT DISTINCT > - > > Key: KYLIN-3453 > URL: https://issues.apache.org/jira/browse/KYLIN-3453 > Project: Kylin > Issue Type: Improvement >Reporter: Chao Long >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > > Currently, Kylin has poor cube size estimation for TOPN, COUNT DISTINCT. We > should improve it, then we can get a reasonable split num when cube building. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3453) Improve cube size estimation for TOPN, COUNT DISTINCT
[ https://issues.apache.org/jira/browse/KYLIN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Long updated KYLIN-3453: - Attachment: image-2018-07-24-15-56-01-150.png > Improve cube size estimation for TOPN, COUNT DISTINCT > - > > Key: KYLIN-3453 > URL: https://issues.apache.org/jira/browse/KYLIN-3453 > Project: Kylin > Issue Type: Improvement >Reporter: Chao Long >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > > Currently, Kylin has poor cube size estimation for TOPN, COUNT DISTINCT. We > should improve it, then we can get a reasonable split num when cube building. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3453) Improve cube size estimation for TOPN, COUNT DISTINCT
[ https://issues.apache.org/jira/browse/KYLIN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Long updated KYLIN-3453: - Attachment: image-2018-07-24-15-53-01-509.png > Improve cube size estimation for TOPN, COUNT DISTINCT > - > > Key: KYLIN-3453 > URL: https://issues.apache.org/jira/browse/KYLIN-3453 > Project: Kylin > Issue Type: Improvement >Reporter: Chao Long >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > > Currently, Kylin has poor cube size estimation for TOPN, COUNT DISTINCT. We > should improve it, then we can get a reasonable split num when cube building. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3453) Improve cube size estimation for TOPN, COUNT DISTINCT
[ https://issues.apache.org/jira/browse/KYLIN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Long updated KYLIN-3453: - Attachment: (was: image-2018-07-24-15-53-01-509.png) > Improve cube size estimation for TOPN, COUNT DISTINCT > - > > Key: KYLIN-3453 > URL: https://issues.apache.org/jira/browse/KYLIN-3453 > Project: Kylin > Issue Type: Improvement >Reporter: Chao Long >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > > Currently, Kylin has poor cube size estimation for TOPN, COUNT DISTINCT. We > should improve it, then we can get a reasonable split num when cube building. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3453) Improve cube size estimation for TOPN, COUNT DISTINCT
[ https://issues.apache.org/jira/browse/KYLIN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Long updated KYLIN-3453: - Attachment: (was: image-2018-07-24-15-52-04-437.png) > Improve cube size estimation for TOPN, COUNT DISTINCT > - > > Key: KYLIN-3453 > URL: https://issues.apache.org/jira/browse/KYLIN-3453 > Project: Kylin > Issue Type: Improvement >Reporter: Chao Long >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > > Currently, Kylin has poor cube size estimation for TOPN, COUNT DISTINCT. We > should improve it, then we can get a reasonable split num when cube building. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3453) Improve cube size estimation for TOPN, COUNT DISTINCT
[ https://issues.apache.org/jira/browse/KYLIN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Long updated KYLIN-3453: - Attachment: (was: image-2018-07-24-15-50-34-462.png) > Improve cube size estimation for TOPN, COUNT DISTINCT > - > > Key: KYLIN-3453 > URL: https://issues.apache.org/jira/browse/KYLIN-3453 > Project: Kylin > Issue Type: Improvement >Reporter: Chao Long >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > > Currently, Kylin has poor cube size estimation for TOPN, COUNT DISTINCT. We > should improve it, then we can get a reasonable split num when cube building. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3453) Improve cube size estimation for TOPN, COUNT DISTINCT
[ https://issues.apache.org/jira/browse/KYLIN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Long updated KYLIN-3453: - Attachment: image-2018-07-24-15-50-34-462.png > Improve cube size estimation for TOPN, COUNT DISTINCT > - > > Key: KYLIN-3453 > URL: https://issues.apache.org/jira/browse/KYLIN-3453 > Project: Kylin > Issue Type: Improvement >Reporter: Chao Long >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > > Currently, Kylin has poor cube size estimation for TOPN, COUNT DISTINCT. We > should improve it, then we can get a reasonable split num when cube building. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3465) kylin Kafka stream incremental build error
chenwen created KYLIN-3465:
--
Summary: kylin Kafka stream incremental build error
Key: KYLIN-3465
URL: https://issues.apache.org/jira/browse/KYLIN-3465
Project: Kylin
Issue Type: Bug
Components: Environment , Streaming
Affects Versions: v2.4.0
Reporter: chenwen
Attachments: image-2018-07-24-14-34-38-102.png
h1. Development environment:
* Centos 7
* Hadoop 2.7.2
* Hbase 1.2.5
* Hive 1.2.2
* Kylin-2.4.0-bin-hbase1x
* Kafka 0.10.2.2
I built a cluster consisting of three machines that build the cube from the
Kafka stream, but each time a new incremental build is made, the following
error is displayed.
{{2018-07-24 14:27:09,269 WARN [Scheduler 268704591 Job
faf6db81-bc76-4b25-b838-8ca993e889d5-602] config.KafkaConsumerProperties:142 :
KYLIN_CONF property was not set, will seek KYLIN_HOME env variable 2018-07-24
14:27:09,295 ERROR [Scheduler 268704591 Job
faf6db81-bc76-4b25-b838-8ca993e889d5-602] hadoop.KafkaFlatTableJob:131 : error
in KafkaFlatTableJob java.lang.NullPointerException at
org.apache.kylin.source.kafka.hadoop.KafkaFlatTableJob.setupMapper(KafkaFlatTableJob.java:143)
at
org.apache.kylin.source.kafka.hadoop.KafkaFlatTableJob.run(KafkaFlatTableJob.java:118)
at
org.apache.kylin.engine.mr.common.MapReduceExecutable.doWork(MapReduceExecutable.java:131)
at
org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:162)
at
org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:69)
at
org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:162)
at
org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:307)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745) 2018-07-24 14:27:09,296 ERROR
[Scheduler 268704591 Job faf6db81-bc76-4b25-b838-8ca993e889d5-602]
common.MapReduceExecutable:138 : error execute
MapReduceExecutable\{id=faf6db81-bc76-4b25-b838-8ca993e889d5-00, name=Save data
from Kafka, state=RUNNING} java.lang.NullPointerException at
org.apache.kylin.source.kafka.hadoop.KafkaFlatTableJob.setupMapper(KafkaFlatTableJob.java:143)
at
org.apache.kylin.source.kafka.hadoop.KafkaFlatTableJob.run(KafkaFlatTableJob.java:118)
at
org.apache.kylin.engine.mr.common.MapReduceExecutable.doWork(MapReduceExecutable.java:131)
at
org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:162)
at
org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:69)
at
org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:162)
at
org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:307)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745) 2018-07-24 14:27:09,302 INFO
[Scheduler 268704591 Job faf6db81-bc76-4b25-b838-8ca993e889d5-602]
execution.ExecutableManager:411 : job
id:faf6db81-bc76-4b25-b838-8ca993e889d5-00 from RUNNING to ERROR 2018-07-24
14:27:09,310 INFO [Scheduler 268704591 Job
faf6db81-bc76-4b25-b838-8ca993e889d5-602] execution.ExecutableManager:411 : job
id:faf6db81-bc76-4b25-b838-8ca993e889d5 from RUNNING to ERROR 2018-07-24
14:27:09,310 DEBUG [Scheduler 268704591 Job
faf6db81-bc76-4b25-b838-8ca993e889d5-602] execution.AbstractExecutable:310 : no
need to send email, user list is empty }}
My current solution is to re-start the service of the job node every time, and
build the incremental build again.
h1. Kylin.properties
kylin.server.mode=job
kylin.server.cluster-servers=99.48.1.2:7070,99.48.1.3:7070
kylin.server.mode=query
kylin.server.cluster-servers=99.48.1.2:7070,99.48.1.3:7070
kylin.server.mode=query
kylin.server.cluster-servers=99.48.1.2:7070,99.48.1.3:7070
99.48.1.1:7070 job
99.48.1.2:7070 query
99.48.1.3:7070 query
Thanks
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
