cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Liu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6102) CassandraStorage broken for bigints and ints
Date Thu, 26 Sep 2013 18:10:05 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13779047#comment-13779047
] 

Alex Liu commented on CASSANDRA-6102:
-------------------------------------

[~jalkanen] Can you try it with CqlStorage which should work? We recommend to use CqlStorage
unless you have to use CassandraStorage. There is some issue with CassandraStorage which can't
get the right validator type for the columns based on system tables. 

We may needs fall back to thrift api to get the metadata for COMPACT STORAGE cql table.
                
> CassandraStorage broken for bigints and ints
> --------------------------------------------
>
>                 Key: CASSANDRA-6102
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6102
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Hadoop
>         Environment: Cassandra 1.2.9 & 1.2.10, Pig 0.11.1, OSX 10.8.x
>            Reporter: Janne Jalkanen
>            Assignee: Alex Liu
>
> I am seeing something rather strange in the way Cass 1.2 + Pig seem to handle integer
values.
> Setup: Cassandra 1.2.10, OSX 10.8, JDK 1.7u40, Pig 0.11.1.  Single node for testing this.

> First a table:
> {noformat}
> > CREATE TABLE testc (
>  key text PRIMARY KEY,
>  ivalue int,
>  svalue text,
>  value bigint
> ) WITH COMPACT STORAGE;
> > insert into testc (key,ivalue,svalue,value) values ('foo',10,'bar',65);
> > select * from testc;
> key | ivalue | svalue | value
> -----+--------+--------+-------
> foo |     10 |    bar |     65
> {noformat}
> For my Pig setup, I then use libraries from different C* versions to actually talk to
my database (which stays on 1.2.10 all the time).
> Cassandra 1.0.12 (using cassandra_storage.jar):
> {noformat}
> testc = LOAD 'cassandra://keyspace/testc' USING CassandraStorage();
> dump testc
> (foo,(svalue,bar),(ivalue,10),(value,65),{})
> {noformat}
> Cassandra 1.1.10:
> {noformat}
> testc = LOAD 'cassandra://keyspace/testc' USING CassandraStorage();
> dump testc
> (foo,(svalue,bar),(ivalue,10),(value,65),{})
> {noformat}
> Cassandra 1.2.10:
> {noformat}
> (testc = LOAD 'cassandra://keyspace/testc' USING CassandraStorage();
> dump testc
> foo,{(ivalue,
> ),(svalue,bar),(value,A)})
> {noformat}
> To me it appears that ints and bigints are interpreted as ascii values in cass 1.2.10.
 Did something change for CassandraStorage, is there a regression, or am I doing something
wrong?  Quick perusal of the JIRA didn't reveal anything that I could directly pin on this.
> Note that using compact storage does not seem to affect the issue, though it obviously
changes the resulting pig format.
> In addition, trying to use Pygmalion 
> {noformat}
> tf = foreach testc generate key, flatten(FromCassandraBag('ivalue,svalue,value',columns))
as (ivalue:int,svalue:chararray,lvalue:long);
> dump tf
> (foo,
> ,bar,A)
> {noformat}
> So no help there. Explicitly casting the values to (long) or (int) just results in a
ClassCastException.

--
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: http://www.atlassian.com/software/jira

Mime
View raw message