You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "nivance (JIRA)" <ji...@apache.org> on 2013/11/06 03:24:20 UTC
[jira] [Reopened] (CASSANDRA-6300) the problem of column family and
table use compositetype as row key
[ https://issues.apache.org/jira/browse/CASSANDRA-6300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
nivance reopened CASSANDRA-6300:
--------------------------------
Reproduced In: 2.0.1
Tester: nivance
h4. It works.Thanks Aleksey.
h4.But another problem comes out.I can select data via thrift but cql3 has not.
{quote}
[default@gxsim] list gameinfo;
Using default limit of 100
Using default cell limit of 100
-------------------
RowKey: key1:key2
=> (name=ltype, value=6c74797065, timestamp=1383703832318000)
1 Row Returned.
Elapsed time: 22 msec(s).
{quote}
{quote}
cqlsh:gxsim> SELECT * FROM gameinfo ;
(0 rows)
{quote}
> the problem of column family and table use compositetype as row key
> -------------------------------------------------------------------
>
> Key: CASSANDRA-6300
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6300
> Project: Cassandra
> Issue Type: Bug
> Components: API
> Environment: cassandra2.0.1 and hector
> Reporter: nivance
> Labels: compositeColumns
>
> h4.The following two scripts 's content is the same but use cassandra-cli and cql.
> h4.cassandra-cli script is :
> {quote}
> create column family gameinfo with comparator = 'UTF8Type'
> and key_validation_class = 'CompositeType(UTF8Type, UTF8Type)'
> AND default_validation_class = UTF8Type
> and column_metadata=[{column_name: ltype, validation_class: UTF8Type}]
> with read_repair_chance=0.1
> and dclocal_read_repair_chance=0.5;
> {quote}
> h4.cql script is :
> {quote}
> CREATE TABLE gameinfo (
> key1 text,
> key2 text,
> ltype text
> PRIMARY KEY ((key1, key2))
> ) ;
> {quote}
> h4.I can insert data use compositetype as row key when using cassandra-cli script, but failed using the cql script.
> h4.So, I think this maybe a bug.
--
This message was sent by Atlassian JIRA
(v6.1#6144)