[
https://issues.apache.org/jira/browse/CASSANDRA-10114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-10114:
---------------------------------------
Attachment: 10114-2.2.txt
The patch allow {{count(*)}} and {{count(1)}} to be selected with other columns
or functions.
I have run CI for 2.2 and 3.0:
* The unit tests results for 2.2 are
[here|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-10114-2.2-testall/lastCompletedBuild/testReport/]
* The Dtests results for 2.2 are
[here|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-10114-2.2-dtest/lastCompletedBuild/testReport/]
* The unit tests results for 3.0 are
[here|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-10114-3.0-testall/lastCompletedBuild/testReport/]
* The Dtests results for 3.0 are
[here|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-10114-3.0-dtest/lastCompletedBuild/testReport/]
> Allow count(*) and count(1) to be use as normal aggregation
> -----------------------------------------------------------
>
> Key: CASSANDRA-10114
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10114
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Benjamin Lerer
> Assignee: Benjamin Lerer
> Priority: Minor
> Fix For: 2.2.x
>
> Attachments: 10114-2.2.txt
>
>
> For the following query:
> {code}
> SELECT count(*), max(timestamp), min(timestamp) FROM myData WHERE id = ?
> {code}
> Cassandra will throw a {{InvalidSyntaxException}}.
> We should allow count(*) and count(1) to be queried with other aggregations
> or columns
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
