cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5867) The Pig CqlStorage/AbstractCassandraStorage classes don't handle collection types
Date Mon, 26 Aug 2013 22:16:53 GMT


Jonathan Ellis commented on CASSANDRA-5867:

Alex, is this ready for review?
> The Pig CqlStorage/AbstractCassandraStorage classes don't handle collection types
> ---------------------------------------------------------------------------------
>                 Key: CASSANDRA-5867
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Hadoop
>            Reporter: Jeremy Hanna
>            Assignee: Alex Liu
>              Labels: pig
>         Attachments: 5867-1.2-branch.txt, 5867-2-1.2-branch.txt, 5867-3-1.2-branch.txt
> The CqlStorage class gets the Pig data type for values from the AbstractCassandraStorage
class, in the getPigType method.  If it isn't a known data type, it makes the value into a
ByteArray.  Currently there aren't any cases there for lists, maps, and sets.
> See this describe output from the grunt shell:
> {code}
> grunt> describe listdata ;                                        
> listdata: {id: (name: chararray,value: int),alist: (name: chararray,value: bytearray),amap:
(name: chararray,value: bytearray),aset: (name: chararray,value: bytearray)}
> {code}
> where the cql data structures had this schema:
> {code}
> CREATE TABLE alltypes (
>   id int PRIMARY KEY,
>   alist list<text>,
>   amap map<text, text>,
>   aset set<text>
> {code}
> It turns out that if you cast the map in grunt to a pig map, then it sort of works, but
I don't think we should probably use a pig map.  Lists don't appear to work at all, as there
is no Pig analogue.  I *think* you could probably just do a UDF to cast these things, but
we already have all of the type information, so we just need to change them to tuples or bags
or whatever.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message