[
https://issues.apache.org/jira/browse/CASSANDRA-14311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16400571#comment-16400571
]
Jeremiah Jordan commented on CASSANDRA-14311:
---------------------------------------------
We would need to add some hints here about the token ranges covered by the
query for the driver to use.
Another method which is used by the Spark connector and the Hadoop connector
before it is for the client side to break up the query by token ranges at the
start, this allows querying multiple token ranges in parallel and gives even
more benefits than just node hopping for the “next” page. You could do this
right now if you just add a new higher level querying interface in a given
driver.
> Allow Token-Aware drivers for range scans
> -----------------------------------------
>
> Key: CASSANDRA-14311
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14311
> Project: Cassandra
> Issue Type: Improvement
> Components: Coordination
> Reporter: Avi Kivity
> Priority: Major
>
> Currently, range scans are not token aware. This means that an extra hop is
> needed for most requests. Since range scans are usually data intensive, this
> causes significant extra traffic.
>
> Token awareness could be enabled by having the coordinator return the token
> for the next (still unread) row in the response, so the driver can select a
> next coordinator that owns this row.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
