User can't manage the lifecycle of THREAD_POOL in Azure Table Storage Java SDK

[luxianlong]

User can't manage the lifecycle of THREAD_POOL in Azure Table Storage Java SDK

[alzimmermsft]

Thanks for posting this @luxianlong, I personally would prefer a case where the ExecutorService can be set externally as this is the most powerful mechanism and could integrate with existing threading logic used within an application. Since you posted this, would your expectation be that this ExecutorService would need to be set before running any SDK operations or could be set at any point during the lifetime of the application?

[luxianlong]

Hi, @alzimmermsft , from my personal perspective, I think the ExecutorService could be set at any point during the lifetime of the application. If you didn't set the ExecutorService, then the application will use the default one.