[
https://issues.apache.org/jira/browse/PHOENIX-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15342768#comment-15342768
]
Lars Hofhansl commented on PHOENIX-3014:
----------------------------------------
Actually removing this part from the patch makes things work:
{code}
this.getTableRef().getTable().getBucketNum() != null ?
SaltingUtil.NUM_SALTING_BYTES : 0,
{code}
> SELECT DISTINCT pk ORDER BY pk DESC gives the wrong results with salted tables
> ------------------------------------------------------------------------------
>
> Key: PHOENIX-3014
> URL: https://issues.apache.org/jira/browse/PHOENIX-3014
> Project: Phoenix
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Fix For: 4.8.0
>
> Attachments: PHOENIX-3014_untested.patch
>
>
> {code}
> create table T(pk1 varchar not null, pk2 varchar not null, constraint pk
> primary key(pk1, pk2)) SALT_BUCKETS=8;
> upsert into T values('1','1');
> upsert into T values('1','2');
> upsert into T values('2','1');
> select /*+ RANGE_SCAN */ distinct(pk1) from T order by pk1 desc;
> +------+
> | PK1 |
> +------+
> | 1 |
> | 2 |
> | 1 |
> select distinct(pk1) from T order by pk1 desc;
> +------+
> | PK1 |
> +------+
> | 1 |
> | 2 |
> | 1 |
> +------+
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
