cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "marius a. eriksen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1016) Coprocessors
Date Sat, 08 May 2010 23:36:51 GMT

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

marius a. eriksen commented on CASSANDRA-1016:
----------------------------------------------

hey Stu - Jeff and i got together today and reworked the patch a bit, 
including writing a trivial distributed indexer.

i think a better name for this is simply "Plugins" (and we've named
it as such in the latest patch).

the code is at:

  http://github.com/mariusaeriksen/cassandra

the current toy indexer simply inverts the mutation in the same CF:

[default@foo] set cf1['row3']['col'] = 'HEYOYO'
Value inserted.
[default@foo] get cf1['HEYOYO']['index']           
=> (column=696e646578, value=row3, timestamp=0)


> Coprocessors
> ------------
>
>                 Key: CASSANDRA-1016
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1016
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Ryan King
>         Attachments: 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