You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Robert Stupp (JIRA)" <ji...@apache.org> on 2014/12/06 00:34:13 UTC
[jira] [Commented] (CASSANDRA-8053) Support for user defined
aggregate functions
[ https://issues.apache.org/jira/browse/CASSANDRA-8053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236305#comment-14236305 ]
Robert Stupp commented on CASSANDRA-8053:
-----------------------------------------
bq. Giving the point above, I'd rather then just stick to Postgres syntax and keep it mandatory for now
+1
It's irrelevant for a running C* instance (and for cqlsh DESCRIBE) since the resolved type is stored in the schema table. But it could mess up creation scripts that might behave differently against different clusters.
> 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)