[CASSANDRA-9890] Bytecode inspection for Java-UDFs

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0 beta 1
• Assignee: Robert Stupp Assign to me
• Reporter: Robert Stupp

Authors

Robert Stupp

Reviewers

T Jake Luciani

• Created: 24/Jul/15 15:00
• Updated: 16/Apr/19 12:31
• Resolved: 31/Jul/15 21:41

Description

(Follow-up to CASSANDRA-9402)

For Java-UDFs we could inspect the compiled Java byte code to find usages of the Java language that are "forbidden" to UDFs.

These include usages of:

• synchronized keyword
• call to j.l.Object.wait
• call to j.l.Object.notify
• call to j.l.Object.notifyAll
• call to j.l.Object.getClass
• calls to specific methods of currently allowed classes in the driver (but would need some investigation)

By inspecting the byte code before the class is actually used, even dirty constructs like the following would be impossible:

CREATE OR REPLACE FUNCTION ... AS $$  return Math.sin(val);
}

{
  // anonymous initializer code
}

static {
  // static initializer code
$$;

(inspired by this blog post)

Issue Links

• links to: Git branch