cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian ONeill (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-1311) Triggers
Date Thu, 08 Nov 2012 01:30:17 GMT


Brian ONeill commented on CASSANDRA-1311:

Ed, you took the words right out of my mouth.  If possible, the classloading should provide
isolation of dependencies. We're struggling with this right now w/ Storm. (See:

It would be great if our solution accounted for this from the get go.  To do this, it might
be necessary to have a separate directory that the users can drop their jars into.  If it
complicates things too much however or delays the implementation, I'd be fine with an initial
version that didn't provide isolation between dependencies.

(BTW -- great to see progress on this)
> Triggers
> --------
>                 Key: CASSANDRA-1311
>                 URL:
>             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,
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message