@vsr1
Yes - but thats the same row by ow iterative approach in a loop. Dont see anything that suggests a BULK fetch is possible via N1QL - only via KV.
I believe calling the execute() on the returned N1QLRequest object should do what you are asking for. Practically speaking, this is no more or less efficient than iterating through it, but it should do what you want.
Well, feel free to benchmark, but behind the scenes, the HTTP fetching code is the same (it fetches the results in chunks into a list of decoded JSON rows) - the iterator just wraps this. But you might theoretically see a small burst of speed, though I haven’t benchmarked it. Bear in mind this will disappear if collating all the results in one list, rather than ‘slurping’ the data, starts to create memory pressure on your OS, encouraging it to swap. Generally most of our APIs are designed to stream large result sets for this reason.