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-7526) Defining UDFs using scripting language directly from CQL
Date Fri, 18 Jul 2014 12:50:05 GMT

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

Robert Stupp commented on CASSANDRA-7526:
-----------------------------------------

Just notes:
* JSR 223 (already available in Java7) allows usage of about two dozen of scriptable languages
- most important are Javascript (Rhino in J7, Nashorn in J8), Groovy, JRuby, Jython.
* Recommend to support only JSR223 providers with compiled script support
* I don't think that we should support all possible languages - just concentrate on the important
ones (need to vote for them and evaluate integration)
* Not sure whether all "supported" languages should be shipped with C* or whether the user
should install them


> Defining UDFs using scripting language directly from CQL
> --------------------------------------------------------
>
>                 Key: CASSANDRA-7526
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7526
>             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
of:
> {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
however.
> 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
(v6.2#6252)

Mime
View raw message