[jira] [Updated] (CASSANDRA-10296) Aggregates aren't resolved properly for reversed types

["Carl Yeksigian (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-10296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carl Yeksigian updated CASSANDRA-10296:
---------------------------------------
    Fix Version/s:     (was: 2.2.x)
                   2.2.2

> Aggregates aren't resolved properly for reversed types
> ------------------------------------------------------
>
>                 Key: CASSANDRA-10296
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10296
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Carl Yeksigian
>            Assignee: Carl Yeksigian
>             Fix For: 2.2.2
>
>
> When using an aggregate, it won't resolve if the column is reversed.
> {code}
> CREATE TABLE t1 (pk int, ck int, PRIMARY KEY (pk, ck)) WITH CLUSTERING ORDER BY (ck DESC)
> SELECT min(ck) FROM t1 WHERE pk = 1
> {code}
> results in the error:
> {noformat}
> Ambiguous call to function min (can be matched by following signatures: system.min : (varint) -> varint, system.min : (int) -> int, system.min : (blob) -> blob): use type casts to disambiguate
> {noformat}
> For aggregates, we should be treating a reversed type the same as we do a normal type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)