[
https://issues.apache.org/jira/browse/CASSANDRA-9230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14509575#comment-14509575
]
Tyler Hobbs commented on CASSANDRA-9230:
----------------------------------------
I agree that CASSANDRA-8831 is the best solution. In the meantime,
CASSANDRA-7923 lowered the server-side impact of the duplicate preparations.
It's also fairly simple for drivers to support async statement preparation, and
preparing the statements concurrently would only be slightly more expensive
than doing them with a single bulk prepare. So, I'm not sure that it's worth
it to add a new protocol feature for bulk preparation right now when
CASSANDRA-8831 will provide the best solution.
> 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
> statements with one round trip to server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
