[
https://issues.apache.org/jira/browse/CASSANDRA-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860933#action_12860933
]
Jonathan Ellis commented on CASSANDRA-1016:
-------------------------------------------
yes, at the very least we need something that uses this before committing.
hand-waving that "we should be able to implement X with this" doesn't cut it.
(to be more specific, we need an X, and we also need a good reason that we're
not committing premature generalization if X could be done more simply without
the "framework" bits.)
> 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.
