cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5576) CREATE/DROP TRIGGER in CQL
Date Thu, 06 Jun 2013 16:17:21 GMT


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:
CREATE CUSTOM INDEX ON <table>(<column>) USING <classname>
with a trigger syntax that would be
CREATE TRIGGER <name> ON <table> EXECUTE <classname>
Knowing that for both we could add support for {{WITH options=\{...\} }} whenever we actually
have options?

> --------------------------
>                 Key: CASSANDRA-5576
>                 URL:
>             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:

View raw message