You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2015/05/09 13:54:00 UTC

[jira] [Commented] (CASSANDRA-9230) Allow preparing multiple prepared statements at once

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

Aleksey Yeschenko commented on CASSANDRA-9230:
----------------------------------------------

CASSANDRA-8831 and CASSANDRA-7923 should indeed be enough.

Also, the protocol is already asynchronous - send all your prepare requests at once, then wait for completion, and you would essentially get the same result in the end. If the drivers don't allow us to do that, then it's a drivers issue, not a C* issue.

So I'm with Tyler on this. Not worth adding a new protocol level construct (-1). Might be worse doing some work on the driver side though.

> Allow preparing multiple prepared statements at once
> ----------------------------------------------------
>
>                 Key: CASSANDRA-9230
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9230
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Vishy Kasar
>            Priority: Minor
>              Labels: ponies
>
> We have a few cases like this:
> 1. Large (40K) clients
> 2. Each client preparing the same 10 prepared statements at the start up and on reconnection to node
> 3. Small(ish) number (24) of cassandra nodes 
> The statement need to be prepared on a casasndra node just once but currently it is prepared 40K times at startup. 
> https://issues.apache.org/jira/browse/CASSANDRA-8831 will make the situation much better. A further optimization is to allow clients to create not-yet prepared statements in bulk.This way, client can prepare all the not yet prepared statements with one round trip to server. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)