[
https://issues.apache.org/jira/browse/CASSANDRA-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669300#comment-13669300
]
Aleksey Yeschenko commented on CASSANDRA-5578:
----------------------------------------------
What we want here is to make trigger_classes column here in
system.schema_columnfamilies to be of set<text> type instead of text.
Also
- cql3 syntax for (with tirgger_classes = <string>) won't do. Has to be a set
(with trigger_classes = {'class1', 'class2', 'class3'})
- alternatively, drop trigger update support from ALTER TABLE completely and
rely on CASSANDRA-5576 instead for trigger creation and removal - we don't want
to have two ways to accomplish the same stuff.
- there is no need to touch/alter cql2 code, it's in life-support mode now
And personally I'd prefer just 'triggers' instead of 'trigger_classes', the
latter is redundant, but ignore this one if you will.
> update trigger schema to use Set instead of CDL text
> ----------------------------------------------------
>
> Key: CASSANDRA-5578
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5578
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0
> Reporter: Jonathan Ellis
> Assignee: Vijay
> Fix For: 2.0
>
> Attachments: 0001-CASSANDRA-5578.patch
>
>
> Should probably name column {{trigger_classes}} or just {{triggers}} too.
> (See
> https://issues.apache.org/jira/browse/CASSANDRA-3919?focusedCommentId=13604931&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13604931
> for why adding pseudo-collections will make life harder as we upgrade.)
--
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
