[
https://issues.apache.org/jira/browse/CASSANDRA-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495364#comment-13495364
]
Jonathan Ellis commented on CASSANDRA-1311:
-------------------------------------------
The same as any other atomic batch when you've disabled commitlog for any of
the CFs involved. (Atomic batch guarantees that the writes are sent to the
replicas, but if you've disabled commitlog then it cannot guarantee that it is
durable.)
> Triggers
> --------
>
> Key: CASSANDRA-1311
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1311
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Maxim Grinev
> Assignee: Vijay
> Fix For: 1.3
>
> Attachments: HOWTO-PatchAndRunTriggerExample.txt,
> HOWTO-PatchAndRunTriggerExample-update1.txt, ImplementationDetails.pdf,
> ImplementationDetails-update1.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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
