cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5576) CREATE/DROP TRIGGER in CQL
Date Tue, 04 Jun 2013 03:27:24 GMT


Vijay commented on CASSANDRA-5576:

Was there an issue with any of the suggestions
Didn't we just drop the options (Map<String, String>) style configuration on CF in CASSANDRA-4795?
Future extension can do simple match on the input parameter which i think is not that bad...

what exactly does it buy us?
It allows the user to group things so they can drop and manage a set of triggers than individual
ones... I am fine dropping that and having one to one relationship (name to class names).

We also don't want to serialize anything as JSON in schema columns anymore

Well it was not just simple type specification in table definition the announce method has
to change, let me spend more time troubleshooting. Hope everything else is alright.

> --------------------------
>                 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