Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[FEATURE REQ] Allow configuration of Reactive Scheduler on SDK or Client level

Abierto
  • ¿Algo no está bien?
#48,827 1 comentario 0 reacciones 2 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@alzimmermsft ya está trabajando en esto.

Desde el 8/8/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

common customer-reported feature-request needs-team-attention

Is your feature request related to a problem? Please describe.

My application has a dedicated thread pool for IO operations that I want to use for azure-sdk async clients (namely eventhubs and blob storage ones) as a Scheduler instead of Schedulers.boundedElastic() but I couldn't find any way to set it across the sdk, or client specific. EventHubClientBuilder has a EventHubClientBuilder scheduler(Scheduler scheduler) method but it's not public. BlobServiceClientBuilder doesn't have such method.

Describe the solution you'd like
Some way to configure Scheduler for all SDK or client basis. Such as

EventHubClientBuilder()
           .connectionString(...)
           .scheduler(customScheduler) // method exist but package private
           .buildAsyncProducerClient()

BlobServiceClientBuilder()
           .scheduler(customScheduler) // method doesn't exist
           .buildAsyncClient()

Describe alternatives you've considered
I'm currently using Mono<T> publishOn(Scheduler scheduler) method but it's kind of error prone. Also I'm not sure that's enough to avoid creation of the Schedulers.boundedElastic() pool for consumer clients. Here's how my code looks now:

eventHubProducerClient.send(data, sendOptions)
               .publishOn(customScheduler)
               .subscribe(...)

Additional context
N/A

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

  • Description Added
  • Expected solution specified
Lenguaje dominante
Java
Estrellas
2.6k
Forks
2.2k
Merge medio
1 d 22 h
PR fusionados (30 d)
220

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Azure/azure-sdk-for-java

Todos los issues de Azure/azure-sdk-for-java

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.