Hi team, Right now, from a stream, an iterator can be obtained which has a blocking hasNext(). So what is the implementation behind the iterator? I assume there must be queue and the iterator monitors the queue. And a separate thread fetches data and feeds to the queue when it is almost empty. If that is the case, no more optimization needs to be done by our users. Please confirm if there is a separate thread that fetches data and feeds to the queue. Thanks.
Regards, Libo
