[
https://issues.apache.org/jira/browse/CASSANDRA-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496333#comment-13496333
]
Ahmet AKYOL commented on CASSANDRA-1311:
----------------------------------------
How about stored procedures? Triggers can't be without them :) Indeed, I don't
believe they are a good fit in C*'s distributed nature( even triggers ??). I
think, the magic words here are once again "eventually-consistent".
Anyway, IMHO, Redis's scripting is also a way to go, maybe a parallel way only
as stored procedures. Redis(2.6.x) has a built-in Lua interpreter, C* can use
Rhino. Redis's [eval|http://redis.io/commands/eval],
[evalsha|http://redis.io/commands/evalsha] and [script
load|http://redis.io/commands/script-load] commands can be used in CQL.
You can also check [the little redis
book|https://github.com/karlseguin/the-little-redis-book/blob/master/en/redis.md]
chapter 5.
> 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
