Olga Natkovich commented on PIG-283:
------------------------------------
We need to clearly document that the value are per script, not per operator or per job and that if value is redefined, the last one will be used for the all jobs in a script.
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.
-------------------------------------------------------------------
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.