[
https://issues.apache.org/jira/browse/CASSANDRA-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860740#action_12860740
]
Stu Hood commented on CASSANDRA-1016:
-------------------------------------
Thanks for taking the initiative here!
Would it be better to configure Callbacks per CF? Otherwise each Callback would
need to have conditionals to ignore CFs they weren't interested in, and they
would need to store whatever state they were concerned with on a per-cf basis.
Also, as jbellis would say: this needs a raison d'etre. Even a really simple
example would be helpful, but perhaps the best way to determine exactly what
the interface needs would be to open another ticket to begin implementing toy
distributed indexes.
> 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.
