[
https://issues.apache.org/jira/browse/CASSANDRA-11521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287116#comment-15287116
]
T Jake Luciani commented on CASSANDRA-11521:
--------------------------------------------
I'm concerned this feature will cause a lot of heap pressure since it's
basically subverting paging. If we added a global bulk request memory space
perhaps OOM could be avoided that way (similar to our new page cache).
As for queuing pages, if you are always going to fetch up to N pages why not
just make the page size N times larger for bulk requests?
In order to detect the speed of the client you can use the
{{Channel.isWritable}} to see if the client isn't able to keep up with the
write watermark see https://issues.apache.org/jira/browse/CASSANDRA-11082
> Implement streaming for bulk read requests
> ------------------------------------------
>
> Key: CASSANDRA-11521
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11521
> Project: Cassandra
> Issue Type: Sub-task
> Components: Local Write-Read Paths
> Reporter: Stefania
> Assignee: Stefania
> Fix For: 3.x
>
>
> Allow clients to stream data from a C* host, bypassing the coordination layer
> and eliminating the need to query individual pages one by one.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
