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,
If you have a consumer listening on a topic and that topic is deleted is the consumer made aware -- perhaps by some exception -- or does it continue listening, blissfully unaware that it will never hear anything more?
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext