[
https://issues.apache.org/jira/browse/PIG-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573112#action_12573112
]
Benjamin Reed commented on PIG-62:
----------------------------------
The query key is going to grow without bound. Should we chop it? Some Pig users
have some really big multistep queries. If they use the embedded Java API and
start iterating, this field could get enormous and a bit meaningless. Perhaps
it would be better to put in just the last line of the query and the line
number. (We would have to start counting semicolons in PigServer...)
> Need to add pig script and input dirs (in clear text format) to jobconf
> -----------------------------------------------------------------------
>
> Key: PIG-62
> URL: https://issues.apache.org/jira/browse/PIG-62
> Project: Pig
> Issue Type: Improvement
> Reporter: Runping Qi
> Attachments: PIG-62-v01.patch, PIG-62-v02.patch
>
>
> We'd like to know what pig query each pig related map/reduce job is for, and
> what input dir the pig job use.
> It will be nice to add pig script and input dirs (in clear text format) to
> the jobconfs of the jobs created for a pig script.
> .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
