[ https://issues.apache.org/jira/browse/PIG-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806503#action_12806503 ]
Ashutosh Chauhan commented on PIG-1124: --------------------------------------- As per previous comment, did manual testing on the patch, no easy way to write unit test. Patch is ready for review. > Unable to set Custom Job Name using the -Dmapred.job.name parameter > ------------------------------------------------------------------- > > Key: PIG-1124 > URL: https://issues.apache.org/jira/browse/PIG-1124 > Project: Pig > Issue Type: Bug > Components: impl > Affects Versions: 0.6.0 > Reporter: Viraj Bhat > Assignee: Ashutosh Chauhan > Priority: Minor > Fix For: 0.7.0 > > Attachments: pig-1124.patch > > > As a Hadoop user I want to control the Job name for my analysis via the > command line using the following construct:: > java -cp pig.jar:$HADOOP_HOME/conf -Dmapred.job.name=hadoop_junkie > org.apache.pig.Main broken.pig > -Dmapred.job.name should normally set my Hadoop Job name, but somehow during > the formation of the job.xml in Pig this information is lost and the job name > turns out to be: > "PigLatin:broken.pig" > The current workaround seems to be wiring it in the script itself, using the > following ( or using parameter substitution). > set job.name 'my job' > Viraj -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.