[
https://issues.apache.org/jira/browse/PIG-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated PIG-283:
---------------------------------
Status: Resolved (was: Patch Available)
Release Note:
For documentation:
After this patch, it becomes possible to set key value pairs as following in
the script.
{code}
set mapred.map.tasks.speculative.execution false
set pig.logfile mylogfile.log
set my.arbitrary.key my.arbitary.value
{code}
These key value pairs would be put in job-conf by Pig. This is a script wide
setting meaning if value is defined multiple times for a key in the script, the
last one will take effect and it will be this value which will be set for all
the jobs generated by script.
Resolution: Fixed
Re-ran all the test reported by Hudson as failures. All of them passed. Patch
committed.
> Allow to set arbitrary jobconf key-value pairs inside pig program
> -----------------------------------------------------------------
>
> Key: PIG-283
> URL: https://issues.apache.org/jira/browse/PIG-283
> Project: Pig
> Issue Type: New Feature
> Components: grunt
> Affects Versions: 0.7.0
> Reporter: Christian Kunz
> Assignee: Ashutosh Chauhan
> Fix For: 0.8.0
>
> Attachments: pig-282.patch
>
>
> It would be useful to be able to set arbitrary JobConf key-value pairs inside
> a pig program (e.g. in front of a COGROUP statement).
> I wonder whether the simplest way to add this feature is by expanding the
> 'set' command functionality.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
