cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9892) Add support for unsandboxed UDF
Date Mon, 03 Aug 2015 09:43:05 GMT


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

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

View raw message