You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2010/07/15 05:06:55 UTC
[jira] Updated: (CASSANDRA-1016) Plugins
[ https://issues.apache.org/jira/browse/CASSANDRA-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-1016:
--------------------------------------
Fix Version/s: 0.8
Affects Version/s: (was: 0.6.1)
Component/s: Core
> Plugins
> -------
>
> Key: CASSANDRA-1016
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1016
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Ryan King
> Assignee: Jeff Hodges
> Fix For: 0.8
>
> Attachments: CASSANDRA-1016-2.patch, CASSANDRA-1016.patch
>
>
> As discussed at the Digg-hosted hackathon.
> First off, this needs a better name, the idea isn't exactly like coprocessors from BigTable and this entry should be considered a stub for now (Stu and Marius should be able to provide more details).
> The idea is that for mutation operations, we should all the user to run a routine that has access to the "old" version of the data and the "new" version, and can take action.
> At a bare minimum, this should be capable of implementing distributed secondary indexes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.