You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Gabriel Reid (JIRA)" <ji...@apache.org> on 2014/03/16 08:20:23 UTC

[jira] [Resolved] (PHOENIX-172) Support the ability for a client to do query more

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

Gabriel Reid resolved PHOENIX-172.
----------------------------------

    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.

> Support the ability for a client to do query more
> -------------------------------------------------
>
>                 Key: PHOENIX-172
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-172
>             Project: Phoenix
>          Issue Type: Task
>    Affects Versions: 2.1.0-Release
>            Reporter: James Taylor
>            Assignee: Samarth Jain
>              Labels: enhancement
>
> Clients often need the ability to "page" through query results that have more row results than are displayable on a single screen. SQL provides LIMIT and OFFSET which is often used for this purpose, however supporting OFFSET in a performant manner is not possible with HBase. Instead, an alternate way of supporting query-more functionality (suggested by @larsh) is through  [row values constructors](http://publib.boulder.ibm.com/infocenter/soliddb/v6r3/index.jsp?topic=/com.ibm.swg.im.soliddb.sql.doc/doc/row.value.constructors.html)  which has been in the SQL spec since SQL-92. It has PostGres support as well with the benefits explained well [here](https://wiki.postgresql.org/images/3/35/Pagination_Done_the_PostgreSQL_Way.pdf) .



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