> "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
>>
>>
>>
>> --
&
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-u
This is very bad news for us :(
Could you please give me reference to jira ticket. I need to track it
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/SELECT-with-ORDER-BY-and-pagination-tp9037p9111.html
Sent from the Apache Ignite Users mailing list archive
ext part of data if needed).
>
> [1]: 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
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
How pagination works with ORDER BY?
Shouldn't client node gets results from all nodes, merge them and re-sort?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/SELECT-with-ORDER-BY-and-pagination-tp9037p9048.html
Sent from the Apache Ignite Users mailing list
o the
next part of data if needed).
[1]: 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
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Let's say I execute
/
select ... from HUGE_REPLICATED_CACHE order by ...
/
Then I fetch few first record of the result cursor
How does it work with pagination? How much RAM do I need at client?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/SELECT-with-ORDER