[jira] [Resolved] (PHOENIX-596) ORDER BY on salted table yields incorrect ordering

["Gabriel Reid (JIRA)" <ji...@apache.org>]

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

Gabriel Reid resolved PHOENIX-596.
----------------------------------

    Resolution: Fixed

Bulk resolve of closed issues imported from GitHub. This status was reached by first re-opening all closed imported issues and then resolving them in bulk.

> ORDER BY on salted table yields incorrect ordering
> --------------------------------------------------
>
>                 Key: PHOENIX-596
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-596
>             Project: Phoenix
>          Issue Type: Task
>    Affects Versions: 2.1.0-Release
>            Reporter: James Taylor
>              Labels: bug, invalid
>
> From Xavier Jodoin (xjodoin at gmail.com) on the mailing list:
> When I do this query on a salt table my results aren't well sort it seem to be sorted only by salt bucket
> SELECT * FROM xawik_log_visit AS log_visit WHERE idsite = 529920360 AND visit_last_action_time >= TO_DATE('2013-09-25 22:00:00') ORDER BY visit_last_action_time DESC LIMIT 10
> The query plan of my query
> +------------+
> |    PLAN    |
> +------------+
> | CLIENT PARALLEL 60-WAY SKIP SCAN ON 20 RANGES OVER XAWIK_LOG_VISIT 0...19,529920360,(*-'2013-09- |
> |     SERVER TOP 10 ROWS SORTED BY [VISIT_LAST_ACTION_TIME] |
> | CLIENT MERGE SORT |
> And my table definition
> CREATE TABLE xawik_log_visit (
>   idsite UNSIGNED_INT not null,
>   visit_last_action_time date not null,
>   idvisit UNSIGNED_INT not null,
>   idvisitor UNSIGNED_INT not null,
>   visit_first_action_time date,
>   txid BIGINT CONSTRAINT pk PRIMARY KEY (idsite, visit_last_action_time desc, idvisit ) ) SALT_BUCKETS = 20;



--
This message was sent by Atlassian JIRA
(v6.2#6252)