cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CASSANDRA-1016) Plugins
Date Fri, 11 Feb 2011 19:36:57 GMT

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

Stu Hood resolved CASSANDRA-1016.
---------------------------------

    Resolution: Duplicate

Resolving as a dupe of CASSANDRA-1311, which is much further along. Thanks for the initial
work here!

> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message