[ https://issues.apache.org/jira/browse/CASSANDRA-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852962#comment-13852962 ]
Brian ONeill commented on CASSANDRA-4914: ----------------------------------------- [~slebresne] agree completely. Maybe as a path forward, I go ahead and implement this in the app layer. That would iron out the storage data model and requisite metadata. Once that is working, we could potentially move it to a trigger (or use CASSANDRA-6412) to make it more generally available. That will also allow us to gauge demand. (potentially we could use this as a use case for the implementation of 6412 as well) > Aggregate functions in CQL > -------------------------- > > Key: CASSANDRA-4914 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4914 > Project: Cassandra > Issue Type: New Feature > Reporter: Vijay > Assignee: Vijay > Fix For: 2.1 > > > 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 was sent by Atlassian JIRA (v6.1.4#6159)