cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9892) Add support for unsandboxed UDF
Date Mon, 03 Aug 2015 09:00:10 GMT

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

Robert Stupp commented on CASSANDRA-9892:
-----------------------------------------

Yea - we need a good name for this. Current proposals are:
UNTRUSTED, TRUSTED, UNFENCED, NON_SANDBOXED

I like TRUSTED (_the user trusts_) or UNFENCED (_no fence around the function_).

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

Mime
View raw message