cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7526) Defining UDFs using scripting language directly from CQL
Date Fri, 18 Jul 2014 16:05:04 GMT


Robert Stupp commented on CASSANDRA-7526:

bq. How many special cases do you anticipate once we restrict to jsr223?

Intention is to keep a minimum of QA to be able to say: "script language _foo_ is fine for
It's ok to publish a "whitelist" (and maybe a "blacklist") of jsr233 implementations which
have been tested in the documentation - it does not need to be implemented in the code.

> Defining UDFs using scripting language directly from CQL
> --------------------------------------------------------
>                 Key: CASSANDRA-7526
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Sylvain Lebresne
> In CASSANDRA-7395 we'll introduce the ability to define user functions by dropping a
java class server side. While this is a good first step and a good option to have in any case,
it would be nice to provide a simpler way to define those functions directly from CQL. And
while we probably don't want to re-invent a new programming language inside CQL, we can reuse
one. Typically, with java 8, we could use nashorn. This would allow a syntax along the lines
> {noformat}
> CREATE FUNCTION sum (a bigint, b bigint) bigint AS { return a + b; }
> {noformat}
> Note that in this, everything before the AS will be parsed by us, which we'll probably
want because we'll probably need to have the types of arguments/return in practice anyway,
and it's a good idea to reuse CQL types. The expression after the AS will be given to Nashorn
> Please note that in theory we could ultimately support multiple language after the AS.
However, I'd like to focus on supporting just one for this ticket and I'm keen on using javascript
through Nashorn because as it's the one that will ship with java from now on, it feels like
a safe default.

This message was sent by Atlassian JIRA

View raw message