You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/06/18 21:21:20 UTC

[jira] [Comment Edited] (CASSANDRA-5649) Move resultset type information into prepare, not execute

    [ https://issues.apache.org/jira/browse/CASSANDRA-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687088#comment-13687088 ] 

Jonathan Ellis edited comment on CASSANDRA-5649 at 6/18/13 7:19 PM:
--------------------------------------------------------------------

P.S. When is globalTablesSpec false?  That is, how do we end up w/ a resultset containing data from more than one CF?
                
      was (Author: jbellis):
    P.S. When is globalTablesSpec false?
                  
> 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