cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stuart Broad <>
Subject Re: Prepared Statement - cache duration (CQL3 - Cassandra 1.2.4)
Date Tue, 23 Apr 2013 10:14:50 GMT
Hi Sorin,

The PreparedQueryNotFoundException is not thrown from
Cassandra.Client>>execute_prepared_cql3_query method.  I created some
prepared statements and then re-started cassandra and received the
following exception:

InvalidRequestException(why: Prepared query with ID 1124421588 not found
(either the query was not prepared on this host (maybe the host has been
restarted?) or you have prepared more than 100000 queries and queries
1124421588 has been evicted from the internal cache))

The best I have been able to come up with is the following:

            try {
                client.execute_prepared_cql3_query(psId, bindValues, ..);
            } catch (InvalidRequestException invEx) {
                String why = invEx.getWhy();
                if(why.startsWith("Prepared query with ID")) {
                    client.execute_prepared_cql3_query(psId, bindValues,
                } else {
                    throw invEx;

Obviously this is pretty fragile and would break if the cassandra message
was changed...but it least it works for now!



On Sun, Apr 21, 2013 at 11:51 AM, Sorin Manolache <> wrote:

> On 2013-04-19 13:57, Stuart Broad wrote:
>> Hi,
>> I am using Cassandra.Client
>> prepare_cql3_query/execute_**prepared_cql3_query to create and run some
>> prepared statements.  It is working well but I am unclear as to how long
>> the server side 'caches' the prepared statements.  Should a prepared
>> statement be prepared for every new Cassandra.Client?  Based on my
>> limited testing it seems like I can create some prepared statements in
>> one Cassandra.Client and use in another but I am not sure how
>> reliable/lasting this is i.e.  If I called the prepared statement again
>> the next day would it still exist?  What about if cassandra was
>> re-started?
>> _Background:_
>> I am creating prepared statements for batch updates of pre-defined
>> lengths (e.g. 10000, 1000, 500, 250, 50, 10, 1) and wanted to know if
>> these could just be set up once.  We felt that using the prepared
>> statements was easier than escaping values within a CQL statement and
>> probably more performant.
>> Thanks in advance for your help.
> I've looked in Cassandra's code (v1.2.3). The cache of prepared statements
> has a size of 100,000. So if you prepare more than 100 thousand statements,
> the least recently used ones will vanish. You'll get the exception
> PreparedQueryNotFoundException**, code 0x2500.
> Regards,
> Sorin

View raw message