[
https://issues.apache.org/jira/browse/CASSANDRA-14311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Lohfink updated CASSANDRA-14311:
--------------------------------------
Comment: was deleted
(was: The driver doesnt actually know if the request is a range scan and doesnt
have a parser. Not quite sure what C* can do here. Maybe a different request
interface in driver for table scans? I think this would be a better ticket for
the driver project as I think people have looked into this before.)
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
