[
https://issues.apache.org/jira/browse/CASSANDRA-9892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651668#comment-14651668
]
Sam Tunnicliffe commented on CASSANDRA-9892:
--------------------------------------------
I wasn't referring to the proposed syntax, but the name of the new element in
the {{o.a.c.auth.Permission}} enum.
That said, what would the intention of {{GRANT TRUST FUNCTION TO ...}} be? It
reads like it should give a role the ability to turn an untrusted function into
a trusted one. I don't see anything in JIRA about adding the ability to change
that post-hoc.
> 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)
