If there’s any chance of using Streaming for this rather than
re-querying the data using CursorMark, it would solve
a lot of these issues.
> On Jun 12, 2019, at 3:26 PM, Mikhail Khludnev wrote:
>
> Every cursorMark request goes through full results. Previous results just
> bypass scoring heap. S
Every cursorMark request goes through full results. Previous results just
bypass scoring heap. So, reducing number of such request should reasonably
reduce wall-clock time exporting all results.
On Wed, Jun 12, 2019 at 11:59 PM Markus Jelsma
wrote:
> Hello,
>
> One of our collections hates Curso
