[jira] Commented: (HIVE-1524) parallel execution failed if mapred.job.name is set

2010-09-29 Thread Yuanjun Li (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12916108#action_12916108
 ] 

Yuanjun Li commented on HIVE-1524:
--

I have done the load test in our company using branch 0.6 with HIVE-1524 patch, 
it seems ok. 
And another interesting thing is the HIVE-1019 problem will be sloved by 
HIVE-1524 as same time, if HIVE-1524 works well with branch 0.6

 parallel execution failed if mapred.job.name is set
 ---

 Key: HIVE-1524
 URL: https://issues.apache.org/jira/browse/HIVE-1524
 Project: Hadoop Hive
  Issue Type: Bug
  Components: Query Processor
Affects Versions: 0.5.0
Reporter: Ning Zhang
Assignee: Ning Zhang
 Fix For: 0.6.0, 0.7.0

 Attachments: HIVE-1524-for-Hive-0.6.patch, HIVE-1524.2.patch, 
 HIVE-1524.patch


 The plan file name was generated based on mapred.job.name. If the user 
 specify mapred.job.name before the query, two parallel queries will have 
 conflict plan file name. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (HIVE-1524) parallel execution failed if mapred.job.name is set

2010-09-28 Thread Ning Zhang (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12915651#action_12915651
 ] 

Ning Zhang commented on HIVE-1524:
--

Thanks for back porting to 0.6 yourchanges. The code changes look good. Can you 
include the other 2 files (parallel.q and parallel.q.out) in the patch as well? 


 parallel execution failed if mapred.job.name is set
 ---

 Key: HIVE-1524
 URL: https://issues.apache.org/jira/browse/HIVE-1524
 Project: Hadoop Hive
  Issue Type: Bug
Affects Versions: 0.5.0
Reporter: Ning Zhang
Assignee: Ning Zhang
 Fix For: 0.7.0

 Attachments: HIVE-1524-for-Hive-0.6.patch, HIVE-1524.2.patch, 
 HIVE-1524.patch


 The plan file name was generated based on mapred.job.name. If the user 
 specify mapred.job.name before the query, two parallel queries will have 
 conflict plan file name. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (HIVE-1524) parallel execution failed if mapred.job.name is set

2010-09-28 Thread Ning Zhang (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12915949#action_12915949
 ] 

Ning Zhang commented on HIVE-1524:
--

Currently branch 0.6 is broken. It may be caused by HIVE-675 patch. I'll run 
test after that one is resolved. 

 parallel execution failed if mapred.job.name is set
 ---

 Key: HIVE-1524
 URL: https://issues.apache.org/jira/browse/HIVE-1524
 Project: Hadoop Hive
  Issue Type: Bug
  Components: Query Processor
Affects Versions: 0.5.0
Reporter: Ning Zhang
Assignee: Ning Zhang
 Fix For: 0.6.0, 0.7.0

 Attachments: HIVE-1524-for-Hive-0.6.patch, HIVE-1524.2.patch, 
 HIVE-1524.patch


 The plan file name was generated based on mapred.job.name. If the user 
 specify mapred.job.name before the query, two parallel queries will have 
 conflict plan file name. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (HIVE-1524) parallel execution failed if mapred.job.name is set

2010-08-10 Thread Joydeep Sen Sarma (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12897037#action_12897037
 ] 

Joydeep Sen Sarma commented on HIVE-1524:
-

will commit once tests pass.

 parallel execution failed if mapred.job.name is set
 ---

 Key: HIVE-1524
 URL: https://issues.apache.org/jira/browse/HIVE-1524
 Project: Hadoop Hive
  Issue Type: Bug
Affects Versions: 0.7.0
Reporter: Ning Zhang
Assignee: Ning Zhang
 Fix For: 0.7.0

 Attachments: HIVE-1524.2.patch, HIVE-1524.patch


 The plan file name was generated based on mapred.job.name. If the user 
 specify mapred.job.name before the query, two parallel queries will have 
 conflict plan file name. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.