[
https://issues.apache.org/jira/browse/PIG-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220476#comment-13220476
]
Bill Graham commented on PIG-2561:
----------------------------------
I've found that {{pig.command.line}} is currently being set on the jobConf via
{{ScriptState}}, so I think we can close this as a won't fix. It includes all
params, both before and after the script file.
If you need to deal with two-word args I'd recommend hooking into the
{{CmdLineParser}}.
My use case FYI, is that I'm working on {{PigProgressNotificationListener}}s
that will collect all relevant script/job metadata (i.e., job stats,
properties, counters, etc.) and store them as either JSON or YAML files (or in
HBase) for archiving. We can then use the job history to better optimize new
job submissions.
> Save Pig command args in PigContext properties
> ----------------------------------------------
>
> Key: PIG-2561
> URL: https://issues.apache.org/jira/browse/PIG-2561
> Project: Pig
> Issue Type: Improvement
> Reporter: Bill Graham
> Assignee: Bill Graham
> Attachments: PIG_2561.1.patch
>
>
> It would be helpful to be able to look at the properties in the PigContext
> and see how a given script was executed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
