[
https://issues.apache.org/jira/browse/CASSANDRA-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683534#comment-13683534
]
Vijay commented on CASSANDRA-5576:
----------------------------------
[~jjordan] the options can be additional columns which can be defined later
(same way we do SCHEMA_COLUMNFAMILIES_CF) when we add them we need to validate
them anyways....
If they are dynamic then they can be additional columns like list<map<String,
map<String, String>> i believe this schema provides a lot of flexibility for
now.
I really dont have a lot of opinion on it, it just was more logical with the
rest of the code (Specially with querying and dropping etc)...
if you want to change it, i can change it. Then we just need to special case
trigger name from the map etc..
> 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
