cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Hodges (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1016) Plugins
Date Sun, 30 May 2010 10:11:39 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873398#action_12873398
] 

Jeff Hodges commented on CASSANDRA-1016:
----------------------------------------

Jan, is your index implementation up somewhere?

> Plugins
> -------
>
>                 Key: CASSANDRA-1016
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1016
>             Project: Cassandra
>          Issue Type: New Feature
>    Affects Versions: 0.6.1
>            Reporter: Ryan King
>            Assignee: Jeff Hodges
>         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.


Mime
View raw message