You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Ning Zhang (JIRA)" <ji...@apache.org> on 2010/08/10 08:33:17 UTC
[jira] Created: (HIVE-1524) parallel execution failed if
mapred.job.name is set
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
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] Updated: (HIVE-1524) parallel execution failed if
mapred.job.name is set
Posted by "yourchanges (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
yourchanges updated HIVE-1524:
------------------------------
Attachment: HIVE-1524-for-Hive-0.6.patch
I have re-upload this patch including parallel.q and parallel.q.out
> 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] Updated: (HIVE-1524) parallel execution failed if
mapred.job.name is set
Posted by "Ning Zhang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ning Zhang updated HIVE-1524:
-----------------------------
Attachment: HIVE-1524.patch
Using UUID to get a unique job ID for each MapRedTask and keep it in the JobConf.
> 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.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] Resolved: (HIVE-1524) parallel execution failed if
mapred.job.name is set
Posted by "Ning Zhang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ning Zhang resolved HIVE-1524.
------------------------------
Release Note: Committed to branch 0.6. Thanks Yuanjun!
Resolution: Fixed
> 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] Updated: (HIVE-1524) parallel execution failed if
mapred.job.name is set
Posted by "Ning Zhang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ning Zhang updated HIVE-1524:
-----------------------------
Attachment: HIVE-1524.patch
> 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.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] Updated: (HIVE-1524) parallel execution failed if
mapred.job.name is set
Posted by "Ning Zhang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ning Zhang updated HIVE-1524:
-----------------------------
Attachment: (was: HIVE-1524.patch)
> 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
>
>
> 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] Updated: (HIVE-1524) parallel execution failed if
mapred.job.name is set
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach updated HIVE-1524:
---------------------------------
Fix Version/s: 0.6.0
Component/s: Query Processor
> 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
Posted by "Ning Zhang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] Updated: (HIVE-1524) parallel execution failed if
mapred.job.name is set
Posted by "Ning Zhang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ning Zhang updated HIVE-1524:
-----------------------------
Status: Patch Available (was: Open)
> 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.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] Updated: (HIVE-1524) parallel execution failed if
mapred.job.name is set
Posted by "Ning Zhang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ning Zhang updated HIVE-1524:
-----------------------------
Attachment: HIVE-1524.2.patch
changed getJobID() to getHiveJobID().
> 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.
[jira] Updated: (HIVE-1524) parallel execution failed if
mapred.job.name is set
Posted by "yourchanges (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
yourchanges updated HIVE-1524:
------------------------------
Attachment: HIVE-1524-for-Hive-0.6.patch
HIVE-1524 backporting to HIVE 0.6 branch
> 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] Updated: (HIVE-1524) parallel execution failed if
mapred.job.name is set
Posted by "Joydeep Sen Sarma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joydeep Sen Sarma updated HIVE-1524:
------------------------------------
Status: Resolved (was: Patch Available)
Resolution: Fixed
committed - thanks Ning.
> 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.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] Updated: (HIVE-1524) parallel execution failed if
mapred.job.name is set
Posted by "Joydeep Sen Sarma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joydeep Sen Sarma updated HIVE-1524:
------------------------------------
Affects Version/s: 0.5.0
(was: 0.7.0)
> 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.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
Posted by "Joydeep Sen Sarma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12896992#action_12896992 ]
Joydeep Sen Sarma commented on HIVE-1524:
-----------------------------------------
looks good to me.
one comment: getJobID is a very confusing name (sounds like we are getting the hadoop jobid or something like that). it would be nice to make it more explicit (getHiveJobID perhaps?).
> 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.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] Updated: (HIVE-1524) parallel execution failed if
mapred.job.name is set
Posted by "yourchanges (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
yourchanges updated HIVE-1524:
------------------------------
Attachment: (was: HIVE-1524-for-Hive-0.6.patch)
> 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] Updated: (HIVE-1524) parallel execution failed if
mapred.job.name is set
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach updated HIVE-1524:
---------------------------------
Affects Version/s: (was: 0.5.0)
Release Note: (was: Committed to branch 0.6. Thanks Yuanjun!)
> parallel execution failed if mapred.job.name is set
> ---------------------------------------------------
>
> Key: HIVE-1524
> URL: https://issues.apache.org/jira/browse/HIVE-1524
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
> Reporter: Ning Zhang
> Assignee: Ning Zhang
> Fix For: 0.6.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] Updated: (HIVE-1524) parallel execution failed if
mapred.job.name is set
Posted by "Ning Zhang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ning Zhang updated HIVE-1524:
-----------------------------
Status: Patch Available (was: Open)
tests are still running now.
> 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.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] Reopened: (HIVE-1524) parallel execution failed if
mapred.job.name is set
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach reopened HIVE-1524:
----------------------------------
Reopening for backport to 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
Posted by "Ning Zhang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] Updated: (HIVE-1524) parallel execution failed if
mapred.job.name is set
Posted by "Ning Zhang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ning Zhang updated HIVE-1524:
-----------------------------
Status: Open (was: Patch Available)
> 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.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] Updated: (HIVE-1524) parallel execution failed if
mapred.job.name is set
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach updated HIVE-1524:
---------------------------------
Fix Version/s: (was: 0.7.0)
> 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
>
> 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
Posted by "Joydeep Sen Sarma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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.
[jira] Commented: (HIVE-1524) parallel execution failed if
mapred.job.name is set
Posted by "Yuanjun Li (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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.