should comment with your use case on the
jira issue.
From: joseph gao [mailto:gaojf.bok...@gmail.com]
Sent: Tuesday, June 16, 2015 10:31 AM
To: user@cassandra.apache.org
Subject: Re: PrepareStatement problem
But I'm using 2.1.6, I still get this bug. So, I should discard that
PrepareStatement
.
>
> There is a reported bug and fixed in 2.1.3. See
> https://issues.apache.org/jira/browse/CASSANDRA-7910
>
>
>
> *From:* joseph gao [mailto:gaojf.bok...@gmail.com]
> *Sent:* Monday, June 15, 2015 10:52 AM
> *To:* user@cassandra.apache.org
> *Subject:* PrepareStatem
@cassandra.apache.org
Subject: PrepareStatement problem
hi, all
I'm using PrepareStatement. If I prepare a sql everytime I use, cassandra
will give me a warning tell me NOT PREPARE EVERYTIME. So I Cache the
PrepareStatement locally . But when other client change the table's schema,
like, add a
hi, all
I'm using PrepareStatement. If I prepare a sql everytime I use,
cassandra will give me a warning tell me NOT PREPARE EVERYTIME. So I Cache
the PrepareStatement locally . But when other client change the table's
schema, like, add a new Column, If I still use the former Cached
PrepareSt
