phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ankit Singhal (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (PHOENIX-3353) Paged Queries: use of LIMIT + OFFSET with ORDER BY
Date Fri, 19 May 2017 05:52:04 GMT

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

Ankit Singhal resolved PHOENIX-3353.
------------------------------------
    Resolution: Duplicate

> Paged Queries: use of LIMIT + OFFSET with ORDER BY
> --------------------------------------------------
>
>                 Key: PHOENIX-3353
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3353
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.8.0, 4.8.1
>         Environment: Phoenix 4.8.1 Hbase 1.2
>            Reporter: Jasper van Ams
>              Labels: limit, offset, orderby, paging
>
> As per documentation (https://phoenix.apache.org/paged.html)
> SELECT * FROM FOO LIMIT 10 OFFSET 10
> returns rows 11 to 20.
> However when adding ORDER BY:
> SELECT * FROM FOO ORDER BY BAR LIMIT 10 OFFSET 10 
> it returns nothing. Only raising the LIMIT with the appropriate OFFSET i.e.
> SELECT * FROM FOO ORDER BY BAR LIMIT 20 OFFSET 10 
> will now return rows 11 to 20
> while
> SELECT * FROM FOO LIMIT 20 OFFSET 10 
> returns rows 11 to 30
> In short: LIMIT + OFFSET in combo with ORDER BY on non primary key has unexpected returns.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message