You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brian ONeill (JIRA)" <ji...@apache.org> on 2013/12/18 21:35:08 UTC
[jira] [Commented] (CASSANDRA-4914) Aggregate functions in CQL
[ https://issues.apache.org/jira/browse/CASSANDRA-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852132#comment-13852132 ]
Brian ONeill commented on CASSANDRA-4914:
-----------------------------------------
Per:
http://www.mail-archive.com/user@cassandra.apache.org/msg33816.html
Is there any interest in extending this functionality to pre-compute aggregations? Basically, enhance the metadata so users can declare which which aggregations they'll want on a table, and along which dimensions. Then, maintain those aggregations in separate CFs as part of the flush/compaction processes (and extend CQL to allow them to be queried).
My feel is that should go under a separate issue. Honestly, I'm just trying to gauge interest for a low-level feature. (akin to secondary indexes)
If there is no interest, I'll just about my business and implement this at the app layer.
> 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)