[
https://issues.apache.org/jira/browse/CASSANDRA-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072731#comment-13072731
]
Martin Hentschel commented on CASSANDRA-1311:
---------------------------------------------
Hi Steve,
Yes, this thread has been silent for quiet some time though we still believe in
our ideas. For research purposes, we evaluated our approach of asynchronous
triggers against the state-of-the-art approach of buffering work items in some
queue outside of Cassandra. Our main findings were the following:
* Our approach requires 15% less machines to perform the same tasks and reduces
overall network traffic by 30%. That is because all work is performed inside
Cassandra instead of outside of Cassandra involving more machines to host the
queue and worker threads that execute work items.
* Our approach gives you the program interface of triggers, which makes it
easier to program applications than writing code to store work items in the
queue and to execute work items with at-least-once semantics.
We now enhanced our ideas towards exactly-once semantics (which were also
favored by Jonathan Ellis in this thread) and an even easier MapReduce-like
programming model. Though, for research purposes, our prototype is not based
on Cassandra anymore. If there is enough interest in our new ideas, we think
it can be easily ported to Cassandra. An in-depth description will be
published soon at the VLDB conference ("Analytics for the Real-Time Web",
http://www.vldb.org/2011/?q=node/23).
Thanks,
Martin
> 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.0
>
> 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
