[
https://issues.apache.org/jira/browse/PIG-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13226196#comment-13226196
]
Ashutosh Chauhan commented on PIG-2576:
---------------------------------------
Until PIG-2344 is resolved this (wanting to know running in front/backend) will
keep coming back, since state is exposed to user, where it should not have
been. Long term fix of this is PIG-2344, in short term we can provide a static
method which can return boolean telling its running in frontend or not, instead
of user doing it themselves and getting into issues.
> Change in behavior for UDFContext.getUDFContext().getJobConf() in front-end
> ---------------------------------------------------------------------------
>
> Key: PIG-2576
> URL: https://issues.apache.org/jira/browse/PIG-2576
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.9.3
> Reporter: Vivek Padmanabhan
> Attachments: PIG-2576_Script_UDF.txt
>
>
> We read a file in the UDF constructor. (The file is transferred to the
> compute nodes via distache)
> To avoid this case in the front-end while the script is in the compile stage,
> we differentiate between front end and back end execution depending upon a
> condition ( UDFContext.getUDFContext().getJobConf() == null )
> This was working till Pig 0.9.1, in the current Pig 0.9 version this is
> breaking.
> ie, If I have any 'fs' commands after the STORE statement, the GruntParser
> invokes the udf constructor again and the above condition check returns false
> causing errors.
--
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
