[CASSANDRA-9892] Add support for unsandboxed UDF

• Type: New Feature
• Status: Open
• Priority: Low
• Resolution: Unresolved
• Fix Version/s: 5.x
• Component/s: Feature/UDF
• Labels: UDF doc-impacting
• Assignee: Robert Stupp
• Reporter: Jonathan Ellis

Authors

Robert Stupp

• Created: 24/Jul/15 13:03
• Updated: 24/Apr/23 12:31

Description

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.

Issue Links

• is related to: CASSANDRA-9402 Implement proper sandboxing for UDFs
• relates to: CASSANDRA-9481 FENCED UDFs
• links to: Git branch