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, 06 Oct 2014 12:04:33 GMT

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

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

As discussed in CASSANDRA-4914 (and with a few others), we should go with the same approach
than prostgres, that is what described at http://www.postgresql.org/docs/8.3/static/sql-createaggregate.html.
In fact, reading that document, I don't seen a good for not going for exactly the same syntax
and behavior (minus a couple stuff that we don't need to support, at least not initially,
like the {{SORTOP}}). An aggregate would thus just be built from existing "scalar" functions
and there is no specific questions about "UDF" flavors to consider.


> 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
>              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
(v6.3.4#6332)

Mime
View raw message