[jira] [Comment Edited] (KYLIN-3311) Segments overlap error
[ https://issues.apache.org/jira/browse/KYLIN-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412880#comment-16412880 ] liyang edited comment on KYLIN-3311 at 3/25/18 5:26 AM: Thanks for reporting. I'm not sure of the root cause yet. It seems the first update was actually successful, however an IllegalStateException was thrown after that, caused a retry, and caused the same segment being added twice. We need to enhance the code to produce more logs first. Then if the problem re-occurs, we can hunt down the root cause. was (Author: liyang.g...@gmail.com): Thanks for reporting. I'm not sure of the root cause yet. It seems the first update was actually successfully, but however an IllegalStateException was thrown after that, caused a retry, and caused the same segment being added twice. I guess we need to enhance the code to produce more logs first. Then if the problem re-occurs, we can hunt down the root cause. > Segments overlap error > -- > > Key: KYLIN-3311 > URL: https://issues.apache.org/jira/browse/KYLIN-3311 > Project: Kylin > Issue Type: Bug > Components: Metadata >Affects Versions: v2.3.0 >Reporter: xujing >Priority: Major > Labels: build > Attachments: Segments_Overlap_ErrorLog.txt > > > when "updateCubeWithRetry" method be called at first time , > line newSegs.validate();was passed . > then > cube = crud.save(cube);seem with error throw exception > write conflict to update cube at try 0 ,will retry... > while retry "updateCubeWithRetry" start > line newSegs.validate();was not passed . > throw exception > Segments overlap: [2018031800_2018031900] and > sales_order_channel[2018031800_201803 > 1900] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3311) Segments overlap error
[ https://issues.apache.org/jira/browse/KYLIN-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412880#comment-16412880 ] liyang commented on KYLIN-3311: --- Thanks for reporting. I'm not sure of the root cause yet. It seems the first update was actually successfully, but however an IllegalStateException was thrown after that, caused a retry, and caused the same segment being added twice. I guess we need to enhance the code to produce more logs first. Then if the problem re-occurs, we can hunt down the root cause. > Segments overlap error > -- > > Key: KYLIN-3311 > URL: https://issues.apache.org/jira/browse/KYLIN-3311 > Project: Kylin > Issue Type: Bug > Components: Metadata >Affects Versions: v2.3.0 >Reporter: xujing >Priority: Major > Labels: build > Attachments: Segments_Overlap_ErrorLog.txt > > > when "updateCubeWithRetry" method be called at first time , > line newSegs.validate();was passed . > then > cube = crud.save(cube);seem with error throw exception > write conflict to update cube at try 0 ,will retry... > while retry "updateCubeWithRetry" start > line newSegs.validate();was not passed . > throw exception > Segments overlap: [2018031800_2018031900] and > sales_order_channel[2018031800_201803 > 1900] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3276) Fix the query cache bug with dynamic parameter
[ https://issues.apache.org/jira/browse/KYLIN-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billy Liu updated KYLIN-3276: - Summary: Fix the query cache bug with dynamic parameter (was: query with dynamic parameter get the same query result) > Fix the query cache bug with dynamic parameter > -- > > Key: KYLIN-3276 > URL: https://issues.apache.org/jira/browse/KYLIN-3276 > Project: Kylin > Issue Type: Bug > Components: Driver - JDBC, Query Engine >Affects Versions: v2.2.0 > Environment: Kylin 2.2.0, JDK 1.8 >Reporter: ZHAOXIXIN >Assignee: nichunen >Priority: Major > Fix For: v2.3.1 > > > sql:"select distinct uid from table where daytime=? limit 70" > ps.setString(1,"2018-01-03") > store the result to ArrayList, and print the size of ArrayList. > when I set the daytime to different dates, the same result I got. > I changed the sql, just change limit value for example > sql:"select distinct uid from table where daytime=? limit 60" > then I got the right value the same like query from GUI:count (distinct uid) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3270) Fix the blocking issue in Cube optimizing job
[ https://issues.apache.org/jira/browse/KYLIN-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billy Liu updated KYLIN-3270: - Summary: Fix the blocking issue in Cube optimizing job (was: Add integration test for Optimize Job) > Fix the blocking issue in Cube optimizing job > - > > Key: KYLIN-3270 > URL: https://issues.apache.org/jira/browse/KYLIN-3270 > Project: Kylin > Issue Type: Sub-task > Components: Tools, Build and Test >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong >Priority: Critical > Fix For: v2.3.1 > > Attachments: APACHE-KYLIN-3270-fix-for-2.3.1.patch, > APACHE-KYLIN-3270-master.patch, APACHE-KYLIN-3270.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3277) Kylin should override hiveconf settings when connecting to hive using jdbc
[ https://issues.apache.org/jira/browse/KYLIN-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billy Liu updated KYLIN-3277: - Fix Version/s: (was: v2.3.1) > Kylin should override hiveconf settings when connecting to hive using jdbc > -- > > Key: KYLIN-3277 > URL: https://issues.apache.org/jira/browse/KYLIN-3277 > Project: Kylin > Issue Type: Bug >Reporter: Chuqian Yu >Priority: Major > Labels: patch > Attachments: 0001-KYLIN-3277.patch > > > Hi, kylin developers. My cube building procedure failing at Step 2 > "Redistribute Flat Hive Table" because Kylin always trying to submit a mr job > to the default yarn queue. > > I have overrided the mapred.job.queue.name property in both > kylin_hive_conf.xml and kylin.properties but it doesn't work. > > kylin.properties > ``` > kylin.source.hive.beeline-params=-n hive -p hive --hiveconf > mapred.job.queue.name=myQueue -u > "jdbc:hive2://myZk:2181/;serviceDiscoveryMode=zooKeeper;" > ``` > > kylin_hive_conf.xml > ``` > > mapred.job.queue.name > myQueue > > ``` > > After digging into the source code ,I found that kylin try to get the row > count of hive table before redistributing it. But it dose not override the > hive configuration when using jdbc to connect to hive server. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KYLIN-3288) "Sqoop To Flat Hive Table" step should specify "mapreduce.queue.name"
[ https://issues.apache.org/jira/browse/KYLIN-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Li resolved KYLIN-3288. Resolution: Fixed > "Sqoop To Flat Hive Table" step should specify "mapreduce.queue.name" > - > > Key: KYLIN-3288 > URL: https://issues.apache.org/jira/browse/KYLIN-3288 > Project: Kylin > Issue Type: Bug > Components: RDBMS Source >Reporter: Shaoxiong Zhan >Assignee: Shaoxiong Zhan >Priority: Major > Fix For: v2.3.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
