ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denis Magda <dma...@apache.org>
Subject Re: SELECT with ORDER BY and pagination
Date Mon, 21 Nov 2016 18:10:48 GMT
Sergi,

Do we already have a ticket for that optimization?

—
Denis

> On Nov 21, 2016, at 4:28 AM, Sergi Vladykin <sergi.vladykin@gmail.com> wrote:
> 
> Right now all the results will be loaded to the client (the reducer node) and will be
resorted. We already working on this issue and hopefully it will be resolved soon.
> 
> Sergi
> 
> 2016-11-17 16:40 GMT+03:00 vdpyatkov <vldpyatkov@gmail.com <mailto:vldpyatkov@gmail.com>>:
> Hi,
> 
> Lock at the method (o.a.i.cache.query.SqlFieldsQuery#setPageSize), that
> allow to set  sql page size.
> If you are going through cursor (result of cache.query()) or executing
> "getAll" then you get all result data.
> 
> Client gets data into page range, if used cursor (and sent request to the
> next part of data if needed).
> 
> [1]: https://apacheignite.readme.io/docs/sql-queries <https://apacheignite.readme.io/docs/sql-queries>
> 
> 
> 
> --
> View this message in context: http://apache-ignite-users.70518.x6.nabble.com/SELECT-with-ORDER-BY-and-pagination-tp9037p9046.html
<http://apache-ignite-users.70518.x6.nabble.com/SELECT-with-ORDER-BY-and-pagination-tp9037p9046.html>
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
> 


Mime
View raw message