<p dir="auto">For historic reasons, scan implementation returns first the count, and then the hits in subsequent requests. While scrolling with regular search returns the first N results immediately.</p>
<p dir="auto">It would be nice if SCAN behaved the same as regular scrolling? Maybe even automatically execute in "scan" mode if sort is set to an empty array or something like that, and scan search type is just a flavor on that?</p>
<p dir="auto">Scrolling with the search_type scan have a different initial response compared with scrolling without scan. Scans do not return documents in the initial response, but regular scrolling does. This can be a bit confusing for end users. According to <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/kimchy/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/kimchy">@kimchy</a>, this difference is no longer required by the implementation, but is maintained for backwards compatibility. It would be nice if at some point in the future we could do away with this difference.</p>