[
https://issues.apache.org/jira/browse/CASSANDRA-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496024#comment-13496024
]
Matthew Brown edited comment on CASSANDRA-1311 at 11/13/12 7:47 AM:
--------------------------------------------------------------------
Or don't implement triggers with code that runs within Cass. Specify an network
endpoint to call with a predefined message containing all details of the
triggering event. Define trigger with connect and read timeouts and retry
instructions (retry on connect failure, don't retry on read timeout, retry x
times, random back off between x-y seconds, etc.)
was (Author: fatpanda):
Or don't implement triggers with code. Specify an network endpoint to call
with a predefined message containing all details of the triggering event.
Define trigger with connect and read timeouts and retry instructions (retry on
connect failure, don't retry on read timeout, retry x times, random back off
between x-y seconds, etc.)
> 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
