You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Carl Yeksigian (JIRA)" <ji...@apache.org> on 2015/09/09 19:25:45 UTC

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

Carl Yeksigian created CASSANDRA-10296:
------------------------------------------

             Summary: 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.x


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)