Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
#48,827 1 条评论 0 个 reaction 已指派 2 人 在 GitHub 查看

维护者通常 1 天内回复

@alzimmermsft 已经在做这个了。

开始于 2026年8月8日。

评估

这个 Issue 还没有评估数据。

描述

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
主要语言
Java
星标
2.6k
派生
2.2k
平均合并
1 天 22 小时
30 天内合并 PR
213

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Azure/azure-sdk-for-java 的其他 Issue

查看 Azure/azure-sdk-for-java 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。