[
https://issues.apache.org/jira/browse/CASSANDRA-16223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-16223:
-----------------------------------------
Status: Ready to Commit (was: Review In Progress)
> Reading dense table yields invalid results in case of row scan queries
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-16223
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16223
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Coordination
> Reporter: Jacek Lewandowski
> Assignee: Jacek Lewandowski
> Priority: Normal
> Fix For: 3.11.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{ThriftIntegrationTest}} is broken in the way that it does not actually test
> reads before and after flushing, because it does not do flush at all (see
> https://github.com/apache/cassandra/blob/cassandra-3.11/test/unit/org/apache/cassandra/cql3/validation/ThriftIntegrationTest.java#L939).
> After fixing that method so that it really flushes memtables to disk, we can
> see inconsistency in reads from dense table - the results returned from
> memtable differs from the results returned from sstable (the later are wrong,
> cell values are skipped unexpectedly).
> {noformat}
> java.lang.AssertionError: Invalid value for row 0 column 0 (value of type
> ascii), expected <value1> but got <>
> {noformat}
> In principle this problems is about skipping column values when doing row
> scan queries with explicitly selected columns (not wildcard), when the
> columns belong to a super column. This happens only when reading from
> sstables, it does not happen when reading from memtables.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
