cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7395) Support for pure user-defined functions (UDF)
Date Wed, 09 Jul 2014 15:55:05 GMT


Robert Stupp commented on CASSANDRA-7395:

bq. Anyway, others may have diverging opinions and I don't feel extremely strongly about that,
just saying that I'm not a fan of adding too much syntax for it.

CREATE FUNCTION bigint math_sum(a bigint, b bigint) {
    return a + b;
would create a UDF in the bundle named "" so a {{SELECT math_sum(col_a, col_b) FROM foo}}
would work as well as {{SELECT math::sum(col_a, col_b) FROM foo}} if there is a UDF bundle
"math". Not sure, whether the "" bundle handling bites named bundles - but it should not.
So users have the option to do it the one or the other way - use unbundled UDFs for simple
things and use bundles to group UDFs.

> Support for pure user-defined functions (UDF)
> ---------------------------------------------
>                 Key: CASSANDRA-7395
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Jonathan Ellis
>              Labels: cql
>             Fix For: 3.0
>         Attachments: 7395-v2.diff, 7395.diff
> We have some tickets for various aspects of UDF (CASSANDRA-4914, CASSANDRA-5970, CASSANDRA-4998)
but they all suffer from various degrees of ocean-boiling.
> Let's start with something simple: allowing pure user-defined functions in the SELECT
clause of a CQL query.  That's it.
> By "pure" I mean, must depend only on the input parameters.  No side effects.  No exposure
to C* internals.  Column values in, result out.

This message was sent by Atlassian JIRA

View raw message