[
https://issues.apache.org/jira/browse/PIG-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831812#action_12831812
]
Olga Natkovich commented on PIG-1215:
-------------------------------------
I would like to request an additional change to make sure that we can write
HadoopId information to the client side log file not just stdout. This would
happen only if special property is used.
So the additional ask is to implement handling of this new property and when it
is present to make sure that all messages at the level of INFO are written to
the log file. This can be accomplished by changing the log listener for the log
file so it picks up INFO level log events.
We don't want to do this by default because it would drastically increase the
number of log files created by Pig since now we only create the file when there
is a real problem executing it.
> Make Hadoop jobId more prominent in the client log
> --------------------------------------------------
>
> Key: PIG-1215
> URL: https://issues.apache.org/jira/browse/PIG-1215
> Project: Pig
> Issue Type: Improvement
> Reporter: Olga Natkovich
> Assignee: Ashutosh Chauhan
> Fix For: 0.7.0
>
> Attachments: pig-1215.patch
>
>
> This is a request from applications that want to be able to programmatically
> parse client logs to find hadoop Ids.
> The woould like to see each job id on a separate line in the following format:
> hadoopJobId: job_123456789
> They would also like to see the jobs in the order they are executed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
