[
https://issues.apache.org/jira/browse/PIG-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142556#comment-13142556
]
Daniel Dai commented on PIG-2338:
---------------------------------
bq. In POUserFunc::setSignature() I think you need to do this.func.sign instead.
Yes, it is good to set signature of EvalFunc once POUserFunc get signature.
Though there is no correctness issue for now, since after that, there is no
more call to EvalFunc in the frontend (outputSchema is the only frontend
EvalFunc call, and it happens in logical layer)
bq. Since this is a new functionality, we should add a e2e testcase covering
this and PIG-2337
I will add a e2e test case.
> Need signature for EvalFunc
> ---------------------------
>
> Key: PIG-2338
> URL: https://issues.apache.org/jira/browse/PIG-2338
> Project: Pig
> Issue Type: New Feature
> Components: impl
> Reporter: Daniel Dai
> Assignee: Daniel Dai
> Fix For: 0.11
>
> Attachments: PIG-2338-1.patch, PIG-2338-1_0.9.patch, PIG-2338-2.patch
>
>
> In LoadFunc/StoreFunc, we generate a unique signature for each
> LoadFunc/StoreFunc, so user can use it as key to retrieve properties in
> UDFContext. We need a similar mechanism for EvalFunc.
--
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
