[
https://issues.apache.org/jira/browse/CASSANDRA-14242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-14242:
------------------------------------------
Fix Version/s: 4.0-beta
> Indexed static column returns inconsistent results
> --------------------------------------------------
>
> Key: CASSANDRA-14242
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14242
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/2i Index
> Environment: Cassandra 3.11.2
> Java driver 3.4.0
> Ubuntu - 4.4.0-112-generic
> Reporter: Ross Black
> Assignee: Andres de la Peña
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0-beta
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> I am using Cassandra 3.11.2, and the Java driver 3.4.0
> I have a table that has a static column, where the static column has a
> secondary index.
> When querying the table I get incomplete or duplicated results, depending on
> the fetch size.
> e.g.
> {code:java}
> CREATE KEYSPACE hack WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': 1};
> CREATE TABLE hack.stuff (id int, kind text, chunk int static, val1 int,
> PRIMARY KEY (id, kind));
> CREATE INDEX stuff_chunk_index ON hack.stuff (chunk);{code}
> -- repeat with thousands of values for id =>
> {code:java}
> INSERT INTO hack.stuff (id, chunk, kind, val1 ) VALUES (${id}, 777, 'A',
> 123);{code}
> Querying from Java:
> {code:java}
> final SimpleStatement statement = new SimpleStatement("SELECT id, kind,
> val1 FROM hack.stuff WHERE chunk = " + chunk);
> statement.setFetchSize(fetchSize);
> statement.setConsistencyLevel(ConsistencyLevel.ALL);
> final ResultSet resultSet = connection.getSession().execute(statement);
> for (Row row : resultSet) {
> final int id = row.getInt("id");
> }{code}
> *The number of results returned depends on the fetch-size.*
> e.g. For 30k values inserted, I get the following:
> ||fetch-size||result-size||
> |40000|30000|
> |20000|30001|
> |5000|30006|
> |100|30303|
> In production, I have a much larger table where the correct result size for a
> specific chunk is 20019, but some fetch sizes will return _significantly
> fewer_ results.
> ||fetch-size||result-size|| ||
> |25000|20019| |
> |5000|9999|*<== this one is has far fewer results*|
> |5001|20026| |
> (so far been unable to reproduce this with the simpler test table)
> Thanks,
> Ross
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
