[
https://issues.apache.org/jira/browse/CASSANDRA-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669381#comment-13669381
]
Aleksey Yeschenko commented on CASSANDRA-5576:
----------------------------------------------
I would drop 'FOR EACH MUTATION' for now - until we have other trigger types
(if we ever do at all).
Also, we might (and probably will) need to store additional info - or at least
add the ability to parametrize triggers. So a column in schema_columnfamilies
won't do (even a map, to keep the names).
We should add another system schema cf, something like this:
{noformat}
CREATE TABLE schema_triggers (
keyspace_name text,
columnfamily_name text,
trigger_name text,
trigger_options map<text, text>,
PRIMARY KEY (keyspace_name, columnfamily_name, trigger_name)
);
{noformat}
And for consistency with CREATE CUSTOM INDEX and other CREATE's, use the
following syntax for CREATE TRIGGER:
{noformat}
CREATE TRIGGER <name> ON <cfname> WITH options = {'class': …, ..}
{noformat}
(Support only 'class' for now).
This makes CASSANDRA-5578 semi-irrelevant, since we are not going to keep
triggers info in schema_columnfamilies anymore.
> CREATE/DROP TRIGGER in CQL
> --------------------------
>
> Key: CASSANDRA-5576
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5576
> Project: Cassandra
> Issue Type: Bug
> Components: API, Core
> Reporter: Jonathan Ellis
> Assignee: Vijay
> Fix For: 2.0
>
>
--
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
