cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8553) Add a key-value payload for third party usage
Date Thu, 12 Mar 2015 09:48:38 GMT


Sylvain Lebresne commented on CASSANDRA-8553:

Well, it's not just going into {{QUERY}} messages, but at least {{EXECUTE}} and {{BATCH}}
too. And probably {{PREPARE}} too since it goes through the {{QueryHandler}} too. And really,
the idea of this is to be as generic as possible, so at least in the spec, it's meant to be
a frame level thing, not something specific to any particular message really. So when I'm
talking about unused flag, I'm not refering to the "query_parameters" one, which would be
inappropriate for this, but rather the frame level one, i.e. the one describe at the section
2.2 of the spec. And we have plenty of space for this one.

bq. What does generic kv payload mean?

The equivalent of a map<string, blob> is what would make the most sense to me. Or, in
the terms of the spec, it would be a:
[kv map]:  A [short] n, followed by n pair <k><v> where <k> is a [string]
and <v> is [bytes].

> Add a key-value payload for third party usage
> ---------------------------------------------
>                 Key: CASSANDRA-8553
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Sergio Bossa
>            Assignee: Robert Stupp
>              Labels: client-impacting, protocolv4
>             Fix For: 3.0
> An useful improvement would be to include a generic key-value payload, so that developers
implementing a custom {{QueryHandler}} could leverage that to move custom data back and forth.

This message was sent by Atlassian JIRA

View raw message