Support binary protocol v3
jbochi opened this issue · comments
Changes from v2:
- stream id is now 2 bytes long (a [short] value), so the header is now 1 byte longer (9 bytes total).
- BATCH messages now have (like QUERY and EXECUTE) and a corresponding optional
<serial_consistency> parameters (see Section 4.1.7).- User Defined Types and tuple types have to added to ResultSet metadata (see 4.2.5.2) and a
new section on the serialization format of UDT and tuple values has been added to the documentation
(Section 7).- The serialization format for collection has changed (both the collection size and
the length of each argument is now 4 bytes long). See Section 6.- 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. As this feature is optionally enabled by clients, implementing it is at the discretion of the
client.- 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.
+1
Hey @thefosk. Could you please elaborate why you are interested in this feature? I think that one possible benefit is that it would be possible to implement named arguments for queries, but this does not have a high priority for me. Thanks.
Oh, missed this issue. Yes, +1, BATCH and named argument as well as default timestamp would be really, really useful
@jbochi Batching would be very useful for executing multiple operations in one request, thus optimizing performance in some scenarios.
@jbochi How do you wish to support v3? Should the library be backwards compatible, handled by the code, should 2 branches be maintained (say 0.x-x and 1.x-x)? Or should the support for v2 be dropped? (knowing that the Python datastax driver is said to only support v3 on their master branch)
My initial thought was that we should provide an option for the user to choose the protocol version on library initialization, but if the official drivers are dropping the v2 support we can do that as well.
Just putting this here for future reference as it took me a ridiculous amount of time to find it (more than 60 seconds...). Binary protocol v3 definition:
I guess very few people have read this document. It's indeed insanely hard
to find. :)
On Wed Feb 18 2015 at 3:33:43 AM Thibault Charbonnier <
notifications@github.com> wrote:
Just putting this here for future reference as it took me a ridiculous
amount of time to find it (more than 60 seconds...)—
Reply to this email directly or view it on GitHub
#22 (comment)
.