he
pagination happens internally. This means that client will fetch rows in
pages discarding old ones, so that you never have more than 10 rows in local
memory at the same time.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Pagination-to-fetch-complete-C
Yes Val, let me try the options
I will get the Ignite from master and check it out
Thanks again Val for timely help
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Pagination-to-fetch-complete-Cache-data-tp3071p3111.html
Sent from the Apache Ignite Users
/Pagination-to-fetch-complete-Cache-data-tp3071p3087.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
"main" javax.cache.CacheException: Failed to run reduce query
locally*.) while using the Query (select * [CacheName]) - is this a bug? -
because with the smaller dataset it works fine.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Pagination-to-fetc
, and they require additional
configuration. Refer to [1] for details.
[1] https://apacheignite.readme.io/docs/sql-queries
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Pagination-to-fetch-complete-Cache-data-tp3071p3073.html
Sent from the Apache Ignite Users