[
https://issues.apache.org/jira/browse/CASSANDRA-15005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773173#comment-16773173
]
A. Soroka commented on CASSANDRA-15005:
---------------------------------------
Hi, [~jmeredithco], thanks very much for checking in!
Do I understand the distinction you're making to be that between:
# UDFs, for which C* is responsible for parsing syntax, developing JVM
bytecode, and distributing the resulting executable function, and
# functions-via-distributed-JARs, in which the _client_ is responsible for all
of those things, and the CQL end of things would just entail a mapping between
a fresh CQL function name and a Java method reference (or something like that) ?
If so, then definitely yes, the latter would resolve my use case deliciously.
I'm after the ability to distribute lightweight computations next to my data,
and I'm happy to organize the management of that process from the client-side;
I don't need or even want to make C* do that work for me.
Did I understand you correctly (I hope!)?
> Configurable whilelist for UDFs
> -------------------------------
>
> Key: CASSANDRA-15005
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15005
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Interpreter
> Reporter: A. Soroka
> Priority: Minor
>
> I would like to use the UDF system to distribute some simple calculations on
> values. For some use cases, this would require access only to some Java API
> classes that aren't on the (hardcoded) whitelist (e.g.
> {{java.security.MessageDigest}}). In other cases, it would require access to
> a little non-C* library code, pre-distributed to nodes by out-of-band means.
> As I understand the situation now, the whitelist for types UDFs can use is
> hardcoded in java in
> [UDFunction|[https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/functions/UDFunction.java#L99].]
> This ticket, then, is a request for a facility that would allow that list to
> be extended via some kind of deployment-time configuration. I realize that
> serious security concerns immediately arise for this kind of functionality,
> but I hope that by restricting it (only used during startup, no exposing the
> whitelist for introspection, etc.) it could be quite practical.
> I'd like very much to assist with this ticket if it is accepted. (I believe I
> have sufficient Java skill to do that, but no real familiarity with C*'s
> codebase, yet. :) )
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
