[
https://issues.apache.org/jira/browse/CASSANDRA-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625382#comment-13625382
]
Sylvain Lebresne commented on CASSANDRA-4914:
---------------------------------------------
bq. For this, the proposal is to add a new AggregateFunction interface for a
function like SUM, which is an extension of Function which takes many arguments?
That's what I had in mind yes. Though AggregateFunction might not be a direct
subclass of Function, maybe they'll just extend the same abstract
class/interface, I haven't looked that closely.
bq. the aggregate function would be iteratively called on each grouping. Is
that accurate?
Exactly. Basically I'm suggesting that the grouping itself can be done
separately by the Selection object since it's completely generic, it doesn't
depend on which aggregate function you'll execute.
> Aggregate functions in CQL
> --------------------------
>
> Key: CASSANDRA-4914
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4914
> Project: Cassandra
> Issue Type: Bug
> Reporter: Vijay
> Assignee: Vijay
> Fix For: 2.0
>
>
> The requirement is to do aggregation of data in Cassandra (Wide row of column
> values of int, double, float etc).
> With some basic agree gate functions like AVG, SUM, Mean, Min, Max, etc (for
> the columns within a row).
> Example:
> SELECT * FROM emp WHERE empID IN (130) ORDER BY deptID DESC;
>
> empid | deptid | first_name | last_name | salary
> -------+--------+------------+-----------+--------
> 130 | 3 | joe | doe | 10.1
> 130 | 2 | joe | doe | 100
> 130 | 1 | joe | doe | 1e+03
>
> SELECT sum(salary), empid FROM emp WHERE empID IN (130);
>
> sum(salary) | empid
> -------------+--------
> 1110.1 | 130
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
