[
https://issues.apache.org/jira/browse/CASSANDRA-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677186#comment-13677186
]
Sylvain Lebresne commented on CASSANDRA-5576:
---------------------------------------------
I don't think I care too much which syntax we pick, though I'm definitely in
favor of more consistency over less.
It does slightly bug me to change the syntax for custom indexes after it's been
release. But, given that nobody is probably using the custom index syntax at
this point (it's not really properly documented yet typically), I'm fine with
it if you guys think it measurably improve the syntax (I have no real opinion
for once on that question). But I'd *really* prefer doing it now rather than
leaving the current syntax in 1.2 and changing it in 2.0.
Though if we do change the custom index syntax, what are we talking about?
Something like:
{noformat}
CREATE CUSTOM INDEX ON <table>(<column>) USING <classname>
{noformat}
with a trigger syntax that would be
{noformat}
CREATE TRIGGER <name> ON <table> EXECUTE <classname>
{noformat}
Knowing that for both we could add support for {{WITH options=\{...\} }}
whenever we actually have options?
> 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
