[
https://issues.apache.org/jira/browse/PIG-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263403#comment-13263403
]
Daniel Dai commented on PIG-2348:
---------------------------------
In the patch, I get rid of the construct Bloom(String filename), which make the
old way (save BuildBloom result into a file, pass to Bloom) not working. I
think we can retain that construct to maintain backward compatibility.
> Bloom should be able to take a relation or a file
> -------------------------------------------------
>
> Key: PIG-2348
> URL: https://issues.apache.org/jira/browse/PIG-2348
> Project: Pig
> Issue Type: Improvement
> Components: internal-udfs
> Affects Versions: 0.11
> Reporter: Alan Gates
> Assignee: Alan Gates
> Priority: Minor
> Fix For: 0.11
>
> Attachments: PIG-2348-0.patch
>
>
> Currently Bloom requires the user to have stored the result of a previous
> query using BuildBloom to an HDFS file before it can be used. This means the
> user must submit an "exec" between this store and the filter that uses Bloom
> if they are to be used in the same script.
> If Bloom could take a relation as its first input (ala the relation cast to
> scalar) then users would not need to put an exec in their script or manage a
> storage location on HDFS.
> Sometimes storing the results in the file makes sense, so we don't want to
> remove the current behavior, just add another option.
--
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
