cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Hentschel (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-1311) Support (asynchronous) triggers
Date Sat, 21 Aug 2010 09:22:19 GMT


Martin Hentschel updated CASSANDRA-1311:

    Attachment: trunk-984391-update2.txt

I fixed the points Stu mentioned:

*  untangled findTriggers
*  using MD5 instead of Arrays.hashCode
*  storing dangling triggers in the System Table instead of Java collections

I want to note that these fixes have introduce some performance penalties.  In our benchmarks
we observed a performance loss of 22%.  According to Maxim who has discussed this point with
Stu at the summit, this is still fine.  The System Table provides additional durability guarantees

> Support (asynchronous) triggers
> -------------------------------
>                 Key: CASSANDRA-1311
>                 URL:
>             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,
> 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:
> An example of using triggers for indexing:
> 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.

View raw message