cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8053) Support for user defined aggregate functions
Date Tue, 04 Nov 2014 11:28:33 GMT


Sylvain Lebresne commented on CASSANDRA-8053:

bq. Branch is based on CASSANDRA-7813 so I've no patch to attach yet

Nobody will get mad if you provide a branch based on some other non-committed branch.

bq. It's pretty much like Postgres syntax except the 'AS' keyword

This is not like the Postgres syntax. In the Postgres syntax, the sfunc and finalfunc are
functions names, not function body. I'm very much in favor of sticking to the Postgres syntax
for now, especially since I suspect this will make it much easier to have function body defined
in only one place in the schema tables. Doing so will remove the need for both {{AS}} and
{{LANGUAGE}} in the aggregate syntax.

> Support for user defined aggregate functions
> --------------------------------------------
>                 Key: CASSANDRA-8053
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Robert Stupp
>            Assignee: Robert Stupp
>              Labels: cql, udf
>             Fix For: 3.0
> CASSANDRA-4914 introduces aggregate functions.
> This ticket is about to decide how we can support "user defined aggregate functions".
UD aggregate functions should be supported for all UDF flavors (class, java, jsr223).
> Things to consider:
> * Special implementations for each scripting language should be omitted
> * No exposure of internal APIs (e.g. {{AggregateFunction}} interface)
> * No need for users to deal with serializers / codecs

This message was sent by Atlassian JIRA

View raw message