[
https://issues.apache.org/jira/browse/CASSANDRA-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676689#comment-13676689
]
Jonathan Ellis commented on CASSANDRA-5576:
-------------------------------------------
bq. I just see no value in being able to bundle several trigger classes under
one name
+1
bq. CREATE TRIGGER indexer ON "Keyspace1"."Standard1" WITH options = {'class':
'org.apache.cassandra.triggers.InvertedIndex'}
-0 -- I see the value of "options" when we introduce parameterization, but
having the actual trigger class be part of that seems odd, since that's
something every trigger needs (i.e. a requirement, not an option or parameter).
So I think I'd prefer to have the EXECUTE syntax, with a single target. We can
add {{WITH options}} later. (But I agree that it's a good idea to split the
triggers into a separate system table to make that easier.)
> 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
