[ 
https://issues.apache.org/jira/browse/CASSANDRA-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979889#action_12979889
 ] 

Jonathan Ellis commented on CASSANDRA-1311:
-------------------------------------------

bq. Of course, there is a window in which triggers have been fired but the 
actual data is not present. If the client ceases to issue the write request, 
then the inconsistency will be durable, which is bad

Right.  This is the biggest valid technical complaint about Cassandra right now 
-- so this design isn't *worse* than the status quo, but I'd like it to be 
*better*. :)

If we said "triggers have to happen within an entity group" (CASSANDRA-1684) 
then we could

- have each replica node process triggers independently, w/o the coordinator 
being involved
- enforce trigger consistency via the commitlog the way 2ary indexes currently 
do



> 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: 0.8
>
>         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.
-
You can reply to this email to add a comment to the issue online.

Reply via email to