Closed mswiderski closed 9 months ago
Hello @mswiderski Thanks for your proposed changes. I totally agree with you that the better solution is to produce an async client:
I believe a real solution to it would be to allow this extension to produce async client as well, which should play much better with reactive code in quarkus.
Are you interested in that?
I think quite soon I will need to use async client as avoiding reactive in quarkus is quite hard :) especially I envision a lot of needs to be used from within reactive messaging code. Though not sure how well reactor and mutiny will work. Have you made any tests on that front?
I think quite soon I will need to use async client as avoiding reactive in quarkus is quite hard :) especially I envision a lot of needs to be used from within reactive messaging code. Though not sure how well reactor and mutiny will work. Have you made any tests on that front?
I haven't looked it into deeper, but I think technically it's doable and useful. Created #181 for tracking the requirement.
@all-contributors please add @mswiderski for code
@majguo
I've put up a pull request to add @mswiderski! :tada:
@mswiderski FYI - We just released 1.0.3
which includes the support of async client for azure-storage-blob. The Quarkus Azure Blob Storage Extension :: Quarkiverse Documentation is also updated accordingly by adding how to use async client in a reactive app.
excellent @majguo thanks a lot for bringing support for async client, much appreciated.
Small addition to the documentation about using azure blob store in reactive code, which essentially does not work and cause a fatal hang of the application.
Quarkus issue reported https://github.com/quarkusio/quarkus/issues/37299 which led to this small though useful (in my opinion) documentation update.
I believe a real solution to it would be to allow this extension to produce async client as well, which should play much better with reactive code in quarkus.