cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Issue Comment Edited: (CASSANDRA-1311) Support (asynchronous) triggers
Date Mon, 16 Aug 2010 00:18:21 GMT


Jonathan Ellis edited comment on CASSANDRA-1311 at 8/15/10 8:17 PM:

bq. A quick glance at the implementation looks like its doing Slave hashing based only on
its IP address, would this cause problems with hosts running multiple Cassandra instances
on a single IP address?

You already can't have multiple Cassandra instances on a single IP.

[the original comment I replied to was deleted, so to avoid losing context, I've edited mine
to include it.]

      was (Author: jbellis):
    You already can't have multiple Cassandra instances on a single IP.
> Support (asynchronous) triggers
> -------------------------------
>                 Key: CASSANDRA-1311
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Contrib
>            Reporter: Maxim Grinev
>             Fix For: 0.8
>         Attachments: HOWTO-PatchAndRunTriggerExample-update1.txt, HOWTO-PatchAndRunTriggerExample.txt,
ImplementationDetails-update1.pdf, ImplementationDetails.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.
You can reply to this email to add a comment to the issue online.

View raw message