cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Petrov (JIRA)" <>
Subject [jira] [Assigned] (CASSANDRA-10786) Include hash of result set metadata in prepared statement id
Date Tue, 10 May 2016 18:48:12 GMT


Alex Petrov reassigned CASSANDRA-10786:

    Assignee: Alex Petrov

> Include hash of result set metadata in prepared statement id
> ------------------------------------------------------------
>                 Key: CASSANDRA-10786
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CQL
>            Reporter: Olivier Michallat
>            Assignee: Alex Petrov
>            Priority: Minor
>             Fix For: 3.x
> 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

View raw message