[ https://issues.apache.org/jira/browse/CASSANDRA-9977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045020#comment-15045020 ]
Sylvain Lebresne commented on CASSANDRA-9977: --------------------------------------------- bq. For a normal {{SELECT}} the type returned within the metadata is {{COUNTER}} but, with the patch, if you use a native aggregate the type returned is {{BIGINT}} I don't think returning one or the other makes much practical difference as {{counter}} and {{bigint}} are pretty much the same thing as far as reads are concerned. I do agree that returning {{counter}} feels more consistent so I would go for that, but that's arguably more of a personal preference than anything else. > Support counter-columns for native aggregates (sum,avg,max,min) > --------------------------------------------------------------- > > Key: CASSANDRA-9977 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9977 > Project: Cassandra > Issue Type: Improvement > Components: CQL > Reporter: Noam Liran > Assignee: Robert Stupp > Fix For: 2.2.x > > > When trying to SUM a column of type COUNTER, this error is returned: > {noformat} > InvalidRequest: code=2200 [Invalid query] message="Invalid call to function > sum, none of its type signatures match (known type signatures: system.sum : > (tinyint) -> tinyint, system.sum : (smallint) -> smallint, system.sum : (int) > -> int, system.sum : (bigint) -> bigint, system.sum : (float) -> float, > system.sum : (double) -> double, system.sum : (decimal) -> decimal, > system.sum : (varint) -> varint)" > {noformat} > This might be relevant for other agg. functions. > CQL for reproduction: > {noformat} > CREATE TABLE test ( > key INT, > ctr COUNTER, > PRIMARY KEY ( > key > ) > ); > UPDATE test SET ctr = ctr + 1 WHERE key = 1; > SELECT SUM(ctr) FROM test; > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)