I don't understand, does the issue mean 'don't use wildcard' or 'already fixed'?
2015-08-26 15:16 GMT+08:00 Peer, Oded <[email protected]>: > See https://issues.apache.org/jira/browse/CASSANDRA-7910 > > > > > > *From:* joseph gao [mailto:[email protected]] > *Sent:* Wednesday, August 26, 2015 6:15 AM > *To:* [email protected] > *Subject:* Re: PrepareStatement BUG > > > > Hi, anybody knows how to resolve this problem? > > > > 2015-08-23 1:35 GMT+08:00 joseph gao <[email protected]>: > > > I'm using cassandra 2.1.7 and datastax java drive 2.1.6 > > Here is the problem: > > > > I use PrepareStatement for query like : SELECT * FROM somespace.sometable > where id = ? > > And I Cached the PrepareStatement in my jvm; > > When the table metadata has changed like a column was added; > > And I use the cached PrepareStament , the data and the metadata(column > definations) don't match. > > So I re-prepare the sql using session.prepare(sql) again, but i see the > code in the async-prepare callback part: > > > > stmt = cluster.manager.addPrepare(stmt); in the SessionManager.java > > > > this will return the previous PrepareStatement. > > So it neither re-prepare automatically nor allow user to re-prepare! > > Is this a bug or I use it like a fool? > > -- > > ------ > > Joseph Gao > > PhoneNum:15210513582 > > QQ: 409343351 > > > > > > -- > > ------ > > Joseph Gao > > PhoneNum:15210513582 > > QQ: 409343351 > -- ------ Joseph Gao PhoneNum:15210513582 QQ: 409343351
