[
https://issues.apache.org/jira/browse/CASSANDRA-8989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369619#comment-14369619
]
Philip Thompson commented on CASSANDRA-8989:
--------------------------------------------
If I flush after the original insert, then disable compaction, and perform the
select multiple times, and flush again, a new sstable shows up. Here is the
output from sstable2json
{code}
[
{"key": "00000001","columns": [["val","val:!",1426781321564999,"t",1426781321]]}
]
{code}
> Reading from table which contains collection type using token function and
> with CL > ONE causes overwhelming writes to replicas
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-8989
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8989
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Miroslaw Partyka
> Assignee: Carl Yeksigian
> Attachments: trace.txt
>
>
> When reading from a table at the aforementioned conditions, each read from
> replica also casues write to the replica.
> Confimed in version 2.0.12 & 2.0.13, version 2.1.3 seems ok.
> To reproduce:
> {code}CREATE KEYSPACE test WITH replication = {'class':
> 'NetworkTopologyStrategy', 'DC1': 2};
> USE test;
> CREATE TABLE bug(id int PRIMARY KEY, val map<int,int>);
> INSERT INTO bug(id, val) VALUES (1, {2: 3});
> CONSISTENCY LOCAL_QUORUM
> TRACING ON
> SELECT * FROM bug WHERE token(id) <= 0;{code}
> trace contains twice:
> Appending to commitlog
> Adding to bug memtable
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
