[
https://issues.apache.org/jira/browse/PIG-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503931#comment-13503931
]
Rohini Palaniswamy commented on PIG-3014:
-----------------------------------------
bq. I don't see a clone happening in mapreduce code. Were you able to get to
the root cause of the behaviour?
I was looking at the wrong version of hadoop code. H23 indeed returns a copy
of the JobConf for jobcontrol.Job. Checked that we don't do a set in other
places. Even the submitted.timestamp that was set was not being used in code
elsewhere before this case. May be it was just set for debugging purposes. So
we should be good with 0.9 and 0.10 for h23.
{code}
public synchronized JobConf getJobConf() {
return new JobConf(super.getJob().getConfiguration());
}
{code}
My +1 as well.
> CurrentTime() UDF has undesirable characteristics
> -------------------------------------------------
>
> Key: PIG-3014
> URL: https://issues.apache.org/jira/browse/PIG-3014
> Project: Pig
> Issue Type: Bug
> Reporter: Jonathan Coveney
> Assignee: Jonathan Coveney
> Fix For: 0.12
>
> Attachments: PIG-3014-0.patch, PIG-3014-1.patch, PIG-3014-2.patch
>
>
> As part of the explanation of the new DateTime datatype I noticed that we had
> added a CurrentTime() UDF. The issue with this UDF is that it returns the
> current time _of every exec invocation_, which can lead to confusing results.
> In PIG-1431 I proposed a way such that every instance of the same NOW() will
> return the same time, which I think is better. Would enjoy thoughts.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
