resourcemanager.cdn.fluent.EndpointsClient blocks thread for > 1 minute

[bhavyakedar]

Query/Question
While using directly using HTTP to call API to purge content in Azure CDN, it returns status 202 immediately. I could not find that support in this SDK.
com.azure.resourcemanager.cdn.fluent.EndpointsClient ---> Async purge methods here use reactive programming and eventually that blocks thread. Developer should be able to choose 'fire & forget' approach here to optimise thread usage and reduce latency.

Why is this not a Bug or a feature Request?
The current code works just fine but is blocking threads for about > 1 min which is not scalable. The feature already exists but it needs to be faster.

Setup (please complete the following information if applicable):

• OS: MAC
• IDE: IntelliJ
• Library/Libraries: 'com.azure.resourcemanager:azure-resourcemanager-cdn:2.31.0'

[joshfree]

@weidongxu-microsoft please take a look

[weidongxu-microsoft]

@bhavyakedar

If you are using EndpointsClient, you can call SyncPoller<> poller = EndpointsClient.beginPurgeContent(..) and it will only send 1 request without polling. I believe this be same as your "directly using HTTP to call API".

You can further call poller.waitForCompletion() to wait for the poll to complete (either successful or failed). I believe this be your "> 1 min" situation.

[weidongxu-microsoft]

I am not sure by "Async purge methods here use reactive programming and eventually that blocks thread", whether you mean purgeContentAsync(..)?

It is Reactor and it shouldn't block (unless you call block()).