There's a similar ticket focusing on range reads and secondary index queries, but the work for these could be done together: https://issues.apache.org/jira/browse/CASSANDRA-10414
On Tue, Oct 18, 2016 at 5:59 PM, Dikang Gu <dikan...@gmail.com> wrote: > Hi there, > > We have couple use cases that are doing fanout read for their data, means > one single read request from client contains multiple keys which live on > different physical hosts. (I know it's not recommended way to access C*). > > Right now, on the coordinator, it will issue separate read commands even > though they will go to the same physical host, which I think is causing a > lot of overheads. > > I'm wondering is it valuable to provide a new read command, that > coordinator can batch the reads to one datanode, and send to it in one > message, and datanode will return the results for all keys belong to it? > > Any similar ideas before? > > > -- > Dikang > -- Tyler Hobbs DataStax <http://datastax.com/>
