cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nate McCall (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-1311) Triggers
Date Mon, 12 Nov 2012 13:31:18 GMT

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

Nate McCall edited comment on CASSANDRA-1311 at 11/12/12 1:31 PM:
------------------------------------------------------------------

bq. Currently there is a JMX to load the new jars and we also watch triggers directory every
minute to looking for new JAR's, I am inclined to removing the watch part for safety and let
the user call the JMX to reload the jar's.

In the use cases I see for this, a timer would not give me enough control in orchestrating
an update to the trigger code. I would much prefer JMX - could be more easily hooked into
nodetool for all at once as well.

(Edit) thought about this update orchestration for a minute, created CASSANDRA-4949 for using
nodetool for such. 
                
      was (Author: zznate):
    bq. Currently there is a JMX to load the new jars and we also watch triggers directory
every minute to looking for new JAR's, I am inclined to removing the watch part for safety
and let the user call the JMX to reload the jar's.

In the use cases I see for this, a timer would not give me enough control in orchestrating
an update to the trigger code. I would much prefer JMX - could be more easily hooked into
nodetool for all at once as well.
                  
> 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

Mime
View raw message