[
https://issues.apache.org/jira/browse/CASSANDRA-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13788596#comment-13788596
]
Alex Liu commented on CASSANDRA-6102:
-------------------------------------
Since thrift structs do not support inheritance, that is, a struct may not
extend other structs, so the choice is to create a new struct CfInfo which has
the following properties
{code}
struct CfInfo {
1: required string keyspace,
2: required string name,
3: optional string column_type="Standard",
4: optional string comparator_type="BytesType",
5: optional string subcomparator_type,
6: optional list<ColumnDef> column_metadata,
7: optional string default_validation_class,
8: optional string key_validation_class,
9: optional boolean compact_cql_table,
10: optional boolean cql3_table
}
{code}
CfInfo is a new struct, so it doesn't affect the other existing code.
or add two additional properties to CfDef
{code}
39: optional boolean compact_cql_table,
40: optional boolean cql3_table
{code}
It adds additional properties only used by Pig, so a little overhead.
> 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
> Attachments: 6102-1.2-branch.txt
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)
