[
https://issues.apache.org/jira/browse/CASSANDRA-11619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Knighton resolved CASSANDRA-11619.
---------------------------------------
Resolution: Duplicate
Given that the reproduction history, presentation, workaround, and reproduction
strategy (as best as I can tell) are identical to [CASSANDRA-11513], I've
resolved this as a duplicate. I can confirm that I cannot reproduce this on
trunk (which will be released as 3.6).
If you have an alternate reproduction that you think still shows this, please
reopen and we'll get to the bottom of it. Thanks.
> "SELECT" returns incorrect result in some cases
> -----------------------------------------------
>
> Key: CASSANDRA-11619
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11619
> Project: Cassandra
> Issue Type: Bug
> Environment: Windows 7, DDC 3.4.0/3.5.0
> Reporter: Stanislaw Stawinsky
>
> In tables like
> "CREATE TABLE test (
> pk uuid,
> ck1 uuid,
> ck2 uuid,
> st text STATIC,
> data text,
> PRIMARY KEY (pk, ck1, ck2)
> );"
> after some inserts in one partition with not empty static column and restart
> of Cassandra, next sequence "insert -> select with same pk an cks" returns
> whole partition, this can be fixed by compaction. Default configuration was
> used.
> "CREATE KEYSPACE keyspace1
> WITH replication = { 'class' : 'SimpleStrategy', 'replication_factor' :
> 1 };"
> was used. Unable to reproduce this on 3.3.0. This might be associated with
> separation of sstables files, exact reason is unknown as well as exact
> conditions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
