cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Lerer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10296) Aggregates aren't resolved properly for reversed types
Date Fri, 11 Sep 2015 09:28:45 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14740467#comment-14740467
] 

Benjamin Lerer commented on CASSANDRA-10296:
--------------------------------------------

+1

I just added an extra unit test to check that everything was fine when the result of a function
has to be assigned to a reversed type.

> 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)

Mime
View raw message