tree 7261fe7b286c0ece7f7fb0b3fc3762cc6708de97
parent 1d9e7b5eba0735c87cfbaa93b0df6455f9c7a339
author Kai Wang <kwang@streamnative.io> 1642006005 +0800
committer GitHub <noreply@github.com> 1642006005 +0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJh3wX1CRBK7hj4Ov3rIwAAeAQIAGAJKau1NImLt5yw9dIDoHgD
 zZ02jPAtJvBbD5zrx69ZnTbGTRTon2FxWns1Yu0HkYnYMj/GC76OMG1wFD8tRuJx
 4rLzpdvqx327WNV1yDm9UikTU7+vV0HK27Ur9HEFR87W+2ANvq1rFBQM/Rgp+wR3
 PbMrsSlw0IwRFzN3bdwl5tviYDPm2zSg9UJH5l4iTuoA0wtaAcmYzfe05ihG7YFW
 SXFW1a75+Q/8I4Qeo9xyQjihpDsqzXyj2SEKdcx7GozQnttBEHF8FOozCxQEDRdB
 Qi4LhmNouCPfAFIwNrs1nbOSb4D21WCLDJmFOz8YlRMUe8V2fQ1DCdzZN2uXb08=
 =IgHw
 -----END PGP SIGNATURE-----
 

Fix the wrong multi-topic has message available behavior (#13634)

Fixes #13605

### Motivation

Currently, the multiTopicReader `hasMessageAvailable` might get the wrong result, we must check `numMessagesInQueue() > 0` again after finish all consumer `hasMessageAvaliableAsync` future, bacause some message might already in `MultiTopicsConsumerImpl#incomingMessages`. 

### Modifications

* Fix the wrong multi-topic has message available behavior.
* Use `reader.readNextAsync()` instead of block method `reader.readNext()`.
* Reduce the units test running time by changing `MultiTopicsReaderTest` to use `@BeforeClass`, `@AfterClass`.