[
https://issues.apache.org/jira/browse/CASSANDRA-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688037#comment-13688037
]
Sylvain Lebresne commented on CASSANDRA-5649:
---------------------------------------------
bq. That is, how do we end up w/ a resultset containing data from more than one
CF?
We never do it for a ResultSet currently, but we reuse ResultSet.Metadata in
responses to prepare messages (to indicate which values has been prepared and
need to be passed to execute), and in that case it can happen (with BATCH). And
since it doesn't really take any space when globalTableSpec == true, we didn't
bothered making a difference for the 2 case.
> Move resultset type information into prepare, not execute
> ---------------------------------------------------------
>
> Key: CASSANDRA-5649
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5649
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jonathan Ellis
> Assignee: Sylvain Lebresne
> Fix For: 2.1
>
>
> Native protocol 1.0 sends type information on execute. This is a minor
> inefficiency for large resultsets; unfortunately, single-row resultsets are
> common.
> This does represent a performance regression from Thrift; Thrift does not
> send type information at all. (Bad for driver complexity, but good for
> performance.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
