cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8053) Support for user defined aggregate functions
Date Mon, 24 Nov 2014 09:28:12 GMT

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

Sylvain Lebresne commented on CASSANDRA-8053:
---------------------------------------------

bq. But we cannot remove STYPE at all - this would not work if there are overloads of SFUNC
with similar argument type

Good point. I guess that's why Postgres has it.

bq. Propose to make STYPE optional and error out, if SFUNC is ambigious

Giving the point above, I'd rather then just stick to Postgres syntax and keep it mandatory
for now. Making it optional would be kind of messy if method overloads of the state transition
function are added after the aggregate has been defined.

> Support for user defined aggregate functions
> --------------------------------------------
>
>                 Key: CASSANDRA-8053
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8053
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Robert Stupp
>            Assignee: Robert Stupp
>              Labels: cql, udf
>             Fix For: 3.0
>
>         Attachments: 8053v1.txt
>
>
> 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
(v6.3.4#6332)

Mime
View raw message