Olivier Michallat created CASSANDRA-10786:
---------------------------------------------
Summary: Include hash of result set metadata in prepared statement
id
Key: CASSANDRA-10786
URL: https://issues.apache.org/jira/browse/CASSANDRA-10786
Project: Cassandra
Issue Type: Improvement
Reporter: Olivier Michallat
Priority: Minor
This is a follow-up to CASSANDRA-7910, which was about invalidating a prepared
statement when the table is altered, to force clients to update their local
copy of the metadata.
There's still an issue if multiple clients are connected to the same host. The
first client to execute the query after the cache was invalidated will receive
an UNPREPARED response, re-prepare, and update its local metadata. But other
clients might miss it entirely (the MD5 hasn't changed), and they will keep
using their old metadata.
One solution that was suggested is to include a hash of the result set metadata
in the prepared statement id. The old id would become invalid, forcing all
clients to reprepare.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
