Repository: cassandra Updated Branches: refs/heads/trunk 551b68e0d -> fb33f383a
Mention that named values are broken for batch (CASSANDRA-10246) in the native protocol spec Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/83fb3cc4 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/83fb3cc4 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/83fb3cc4 Branch: refs/heads/trunk Commit: 83fb3cc42209d27ad8b906a17df64832b3f84fb0 Parents: 7f1fec1 Author: Sylvain Lebresne <sylv...@datastax.com> Authored: Fri Oct 30 09:47:35 2015 +0100 Committer: Sylvain Lebresne <sylv...@datastax.com> Committed: Fri Oct 30 09:47:45 2015 +0100 ---------------------------------------------------------------------- doc/native_protocol_v3.spec | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/cassandra/blob/83fb3cc4/doc/native_protocol_v3.spec ---------------------------------------------------------------------- diff --git a/doc/native_protocol_v3.spec b/doc/native_protocol_v3.spec index 312c8c1..087e138 100644 --- a/doc/native_protocol_v3.spec +++ b/doc/native_protocol_v3.spec @@ -394,7 +394,11 @@ Table of Contents will still override this timestamp. This is entirely optional. 0x40: With names for values. If set, then all values for all <query_i> must be preceded by a [string] <name_i> that have the same meaning as in QUERY - requests. + requests [IMPORTANT NOTE: this feature does not work and should not be + used. It is specified in a way that makes it impossible for the server + to implement. This will be fixed in a future version of the native + protocol. See https://issues.apache.org/jira/browse/CASSANDRA-10246 for + more details]. - <n> is a [short] indicating the number of following queries. - <query_1>...<query_n> are the queries to execute. A <query_i> must be of the form: @@ -1023,9 +1027,10 @@ Table of Contents * QUERY, EXECUTE and BATCH messages can now optionally provide the default timestamp for the query. As this feature is optionally enabled by clients, implementing it is at the discretion of the client. - * QUERY, EXECUTE and BATCH messages can now optionally provide the names for the values of the + * QUERY and EXECUTE messages can now optionally provide the names for the values of the query. As this feature is optionally enabled by clients, implementing it is at the discretion of the - client. + client (Note that while the BATCH message has a flag for this, it actually doesn't work for BATCH, + see Section 4.1.7 for details). * The format of "Schema_change" results (Section 4.2.5.5) and "SCHEMA_CHANGE" events (Section 4.2.6) has been modified, and now includes changes related to user types.
