Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 23 Mar 2015 09:07:11 +0000 (UTC)
From: "Robert Stupp (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12764522.1420207768000.4790.1427101631696@Atlassian.JIRA>
In-Reply-To: <JIRA.12764522.1420207768000@Atlassian.JIRA>
References: <JIRA.12764522.1420207768000@Atlassian.JIRA>
 <JIRA.12764522.1420207768846@arcas>
Subject: [jira] [Updated] (CASSANDRA-8553) Add a key-value payload for third
 party usage
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-8553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Stupp updated CASSANDRA-8553:
------------------------------------
    Attachment: 8553-v3.txt

Attached v3 with the review comments worked in.

> Add a key-value payload for third party usage
> ---------------------------------------------
>
>                 Key: CASSANDRA-8553
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8553
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Sergio Bossa
>            Assignee: Robert Stupp
>              Labels: client-impacting, protocolv4
>             Fix For: 3.0
>
>         Attachments: 8553-v2.txt, 8553-v3.txt, 8553.txt
>
>
> 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
(v6.3.4#6332)