>From this document https://apacheignite-sql.readme.io/docs/performance-and-debugging#section-result-set-lazy-load, it mentioned that when setting lazy load flag on the query it can avoid prolonged GC pauses and even OutOfMemoryError.
But it confuses me how does lazy load work internally in Ignite? Does Ignite send part of the result set to the client? If Ignite is still sending whole result set back to the client, how can lazy load avoid loading full result set on heap? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
