cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5649) Move resultset type information into prepare, not execute
Date Mon, 17 Jun 2013 18:05:23 GMT


Jonathan Ellis commented on CASSANDRA-5649:

Comparing prior art shows that both MySQL and PostgreSQL send type information for each execution,
but I cannot find a reason for this other than historical accident.  A postgresql developer
confirmed that a prepared statement *must* return the same types with each call, so theoretically
there should be no obstacle in only returning types once.
> Move resultset type information into prepare, not execute
> ---------------------------------------------------------
>                 Key: CASSANDRA-5649
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>            Assignee: Sylvain Lebresne
>             Fix For: 2.0
> 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:

View raw message