[ https://issues.apache.org/jira/browse/CASSANDRA-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096236#comment-13096236 ]
Jonathan Ellis commented on CASSANDRA-1311: ------------------------------------------- Fundamentally there is zero value to an app developer from coordinator-run triggers vs running the same code from a well-designed app-side storage layer. This is why I don't think it's worth adding a bunch of fragile scaffolding around it to try to make it kinda halfway work. But replica-level triggers are not simply moving logic from the client to the coordinator. That makes it more interesting, as well as trivially sound via the commitlog. > Support (asynchronous) triggers > ------------------------------- > > Key: CASSANDRA-1311 > URL: https://issues.apache.org/jira/browse/CASSANDRA-1311 > Project: Cassandra > Issue Type: New Feature > Components: Contrib > Reporter: Maxim Grinev > Fix For: 1.1 > > Attachments: HOWTO-PatchAndRunTriggerExample-update1.txt, > HOWTO-PatchAndRunTriggerExample.txt, ImplementationDetails-update1.pdf, > ImplementationDetails.pdf, trunk-967053.txt, trunk-984391-update1.txt, > trunk-984391-update2.txt > > > Asynchronous triggers is a basic mechanism to implement various use cases of > asynchronous execution of application code at database side. For example to > support indexes and materialized views, online analytics, push-based data > propagation. > Please find the motivation, triggers description and list of applications: > http://maxgrinev.com/2010/07/23/extending-cassandra-with-asynchronous-triggers/ > An example of using triggers for indexing: > http://maxgrinev.com/2010/07/23/managing-indexes-in-cassandra-using-async-triggers/ > Implementation details are attached. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira