[
https://issues.apache.org/jira/browse/CASSANDRA-6871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937978#comment-13937978
]
Jonathan Ellis commented on CASSANDRA-6871:
-------------------------------------------
Ultimately what I'd like to see is CREATE TRIGGER specify a UDF, with UDF
support for multiple languages a la postgresql, but I'm not sure if this is a
step in that direction. It sounds like I'd still be shipping jars around, so
I'm not sure what you're proposing besides some kind of groovy support.
Did you mean to provide a link to the branch above?
> Dynamic class loading for triggers (and udfs)
> ---------------------------------------------
>
> Key: CASSANDRA-6871
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6871
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Edward Capriolo
> Assignee: Edward Capriolo
>
> Currently the trigger feature requires out of band shipping jar files to
> servers. In the near future users may be able to provide custom functions
> like trim() dynamically like pig and hive do. In order to accomplish this
> securely my suggestion is this.
> 1. Add a new configuration knob to cassandra.yaml which controls how users
> are allowed to load class definitions.
> {code}
> dynamic_loading:
> - JAVA_LOCAL_CLASSPATH
> - GROOVY_CLASS_LOADER
> {code}
> 2. Add the https://github.com/edwardcapriolo/nit-compiler to the project as a
> dependency.
> 3. Profit: A follow on piece would allow triggers to be defined in a JVM
> language. Features like https://issues.apache.org/jira/browse/CASSANDRA-6870
> could use this. Users can also create different pluggable components to CQL
> at runtime.
> This issue would just be about brining the dynamic loading mechanism in the
> project securely. Not implementing it in a user facincg way.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
