[
https://issues.apache.org/jira/browse/CASSANDRA-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127743#comment-13127743
]
Gopalakrishnan Rajagopal commented on CASSANDRA-3360:
-----------------------------------------------------
I am not too sure... the same hector version and code works with 1.0.0-beta1
version though. So this just is a compatibilty issue with 1.0.0-rc2?
> Read data inconsistancy in Cassandra 1.0.0-rc2
> ----------------------------------------------
>
> Key: CASSANDRA-3360
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3360
> Project: Cassandra
> Issue Type: Bug
> Components: API
> Affects Versions: 1.0.0
> Reporter: Gopalakrishnan Rajagopal
>
> When qsuper column for a particular key is being queried
> using hector-core-0.8.0-2,
> the data retrieved is inconsistent. I mean, for the key that I use to fetch
> data, there are 7 sub columns actually. But the query returns 1 or 3 sub
> columns depending on which nodes respond to it. (I tested by bringing down
> each one of the three nodes in turn).
> When I tried to fetch the data for the same key using cassandra-cli tool, I
> get all the 7 sub columns for both the consistancy levels ONE and QUORUM.
> Below is the code that I used to fetch data
> superColumnQuery = HFactory.createSuperColumnQuery
> (keyspaceOperator,
> stringSerializer,
> stringSerializer, stringSerializer, stringSerializer);
> superColumnQuery.setColumnFamily(cfName).setKey
> (key).setSuperName(scName);
> result=superColumnQuery.execute();
> superColumn=result.get();
> columnList=superColumn.getColumns();
--
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
