You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Brandon Williams (Resolved) (JIRA)" <ji...@apache.org> on 2012/02/22 02:22:48 UTC

[jira] [Resolved] (CASSANDRA-3356) Add more data type checks when storing data from Pig to Cassandra

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

Brandon Williams resolved CASSANDRA-3356.
-----------------------------------------

    Resolution: Fixed

Think I got this one in CASSANDRA-3886.
                
> Add more data type checks when storing data from Pig to Cassandra
> -----------------------------------------------------------------
>
>                 Key: CASSANDRA-3356
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3356
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.8.7
>            Reporter: Jeremy Hanna
>            Priority: Minor
>              Labels: pig
>
> Pre-CASSANDRA-2810, the decompose method was tried before assuming the data was of type DataByteArray.  It needs to have both - first a check to see if it can be decomposed.  If that doesn't work (exception) it can try the cast.  If that doesn't work, then we can't store the object - or as Brandon says, we need to put another special case in ObjToBB.  This is all based on a conversation in IRC with Brandon Williams, Jacob Perkins, and Jeremy Hanna about a problem arising when trying to store an object of type long to Cassandra.

--
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