[
https://issues.apache.org/jira/browse/CASSANDRA-9892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651630#comment-14651630
]
Sam Tunnicliffe commented on CASSANDRA-9892:
--------------------------------------------
The problem with {{TRUSTED}} (and also any of the suggestions above) is that it
doesn't describe an action (or set of actions) which the permission allows.
Existing permissions are all verbs, which shows this nicely. I also haven't
looked at the patch in detail yet, but off the top of my head something like
{{CREATE_TRUSTED}} is the best I can come up with (and to be clear that I
don't like that very much either).
> Add support for unsandboxed UDF
> -------------------------------
>
> Key: CASSANDRA-9892
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9892
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jonathan Ellis
> Assignee: Robert Stupp
> Priority: Minor
>
> From discussion on CASSANDRA-9402,
> The approach postgresql takes is to distinguish between "trusted" (sandboxed)
> and "untrusted" (anything goes) UDF languages.
> Creating an untrusted language always requires superuser mode. Once that is
> done, creating functions in it requires nothing special.
> Personally I would be fine with this approach, but I think it would be more
> useful to have the extra permission on creating the function, and also
> wouldn't require adding explicit CREATE LANGUAGE.
> So I'd suggest just providing different CQL permissions for trusted and
> untrusted, i.e. if you have CREATE FUNCTION permission that allows you to
> create sandboxed UDF, but you can only create unsandboxed if you have CREATE
> UNTRUSTED.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
