Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C6C9B173BA for ; Thu, 23 Apr 2015 18:05:39 +0000 (UTC) Received: (qmail 45497 invoked by uid 500); 23 Apr 2015 18:05:39 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 45446 invoked by uid 500); 23 Apr 2015 18:05:39 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 45433 invoked by uid 99); 23 Apr 2015 18:05:39 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Apr 2015 18:05:39 +0000 Date: Thu, 23 Apr 2015 18:05:39 +0000 (UTC) From: "Vishy Kasar (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CASSANDRA-9230) Allow preparing multiple prepared statements at once MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Vishy Kasar created CASSANDRA-9230: -------------------------------------- Summary: Allow preparing multiple prepared statements at once Key: CASSANDRA-9230 URL: https://issues.apache.org/jira/browse/CASSANDRA-9230 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Vishy Kasar 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)