[
https://issues.apache.org/jira/browse/CASSANDRA-11521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235601#comment-15235601
]
DOAN DuyHai commented on CASSANDRA-11521:
-----------------------------------------
bq. with each row, we both repeat all the clustering columns - even if many
rows share them - and the partition key columns. Could get rid of it, and all
related redundant serialisation, if not building on top of ResultSet.
I had this remark a long time ago back in 2014 and people told me that thanks
to network compression there is no much wasted bandwidth indeed.
What I had in mind back then was to send **raw** data to the driver and the
driver will be responsible to de-serialize and re-format the data to have a
proper _CQL row representation_
But it means putting a bunch of extra-logic and overhead on the client side,
not sure the core team agrees on this point
> 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)
