The protocol does already support optional/custom payloads to do such things.
IIRC the zipkin tracing implementation
https://github.com/thelastpickle/cassandra-zipkin-tracing for example uses this
to pass the zipkin id to the server.
> On Apr 20, 2018, at 1:02 PM, Max C. wrote:
>
> For thing
For things like #3, would it be a better idea to propose a generic enhancement
for “optional vendor extensions” to the protocol? These extensions would be
negotiated during connection formation and then the driver could (optionally)
implement these additional features. These extensions would b
>
>
> Those were just given as examples. Each would be discussed on its own,
> assuming we are able to find a way to cooperate.
>
>
> These are relatively simple and it wouldn't be hard for use to patch
> Cassandra. But I want to find a way to make more complicated protocol
> changes where it would
