You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2015/08/03 10:51:05 UTC

[jira] [Commented] (CASSANDRA-9892) Add support for unsandboxed UDF

    [ https://issues.apache.org/jira/browse/CASSANDRA-9892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651608#comment-14651608 ] 

Aleksey Yeschenko commented on CASSANDRA-9892:
----------------------------------------------

/cc [~beobal]

Haven't looked at the patch in detail, yet, but {{TRUSTED}} is not a proper name for a permission.

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