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

Patrick McFadin commented on CASSANDRA-1311:
--------------------------------------------

I love the idea of having triggers but I'm less than enthusiastic about adding 
operation overhead in deploying jar files to every node. When you are talking 
about a cluster with 100s of nodes, that's going to be a lot of files to copy 
around.

Here's a radical idea. Why not store the jar file in a CF? 
* The jars will be distributed and available to all nodes in the cluster.
* When backing up and restoring a node, this won't add any extra steps.
* When new nodes come online, everything for the trigger will be a part of the 
bootstrap.

I'm saying this strictly from an operations standpoint. 
                
> 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

Reply via email to