You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benjamin Lerer (Jira)" <ji...@apache.org> on 2021/06/07 10:10:00 UTC

[jira] [Created] (CASSANDRA-16717) The fetching strategy can be optimized for CL.ONE and CL.LOCAL_ONE

Benjamin Lerer created CASSANDRA-16717:
------------------------------------------

             Summary: The fetching strategy can be optimized for CL.ONE and CL.LOCAL_ONE
                 Key: CASSANDRA-16717
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16717
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Benjamin Lerer
            Assignee: Benjamin Lerer


The current {{ColumnFilter}} fetching strategy has been implemented in order to guaranty the CQL semantics around empty vs non-existing rows. It has also some importance regarding read-repair (CASSANDRA-16710). Nevertheless, reads at {{CL.ONE}} and at {{CL.LOCAL_ONE}} do not use read-repair and do not require more columns than the queried ones as those cannot be deleted by column deletions present on other nodes. By consequence, having {{ColumnFilter}} fetching only the queried columns should improve query speed, by reducing the number of SSTable reads for queries fetching specific rows and reducing the amound of data serialized and transfered between nodes (if the data is not local). 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org