[ 
https://issues.apache.org/jira/browse/CASSANDRA-2869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jeremy Hanna updated CASSANDRA-2869:
------------------------------------

    Attachment: 2869-2.txt

Removed that String.  Also removed adding mutation twice and put in the nested 
exception in putNext into the IOException.  We've been meaning to add those 
last two items to one of these tickets.

> CassandraStorage does not function properly when used multiple times in a 
> single pig script due to UDFContext sharing issues
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-2869
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2869
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Contrib
>    Affects Versions: 0.7.2
>            Reporter: Grant Ingersoll
>            Assignee: Jeremy Hanna
>         Attachments: 2869-2.txt, 2869.txt
>
>
> CassandraStorage appears to have threading issues along the lines of those 
> described at http://pig.markmail.org/message/oz7oz2x2dwp66eoz due to the 
> sharing of the UDFContext.
> I believe the fix lies in implementing
> {code}
> public void setStoreFuncUDFContextSignature(String signature)
>     {
>     }
> {code}
> and then using that signature when getting the UDFContext.
> From the Pig manual:
> {quote}
> setStoreFunc!UDFContextSignature(): This method will be called by Pig both in 
> the front end and back end to pass a unique signature to the Storer. The 
> signature can be used to store into the UDFContext any information which the 
> Storer needs to store between various method invocations in the front end and 
> back end. The default implementation in StoreFunc has an empty body. This 
> method will be called before other methods.
> {quote}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to