Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

[CosmosDB] Feature Request: Support Vert.x HTTP Client or Pluggable HTTP Client Implementation

オープン
  • 何か問題がありますか？
#49,166 コメント 1 件 リアクション 1 件 担当者 4 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@pjohari-ms がすでに取り組んでいます。

2026年8月8日 から。

評価

この issue はまだ評価されていません。

説明

Client Cosmos customer-reported feature-request needs-team-attention Service Attention

Is your feature request related to a problem? Please describe.
The Azure CosmosDB SDK currently hardcodes the use of reactor-netty HTTP client in its implementation (see ReactorNettyClient.java (https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/cosmos/azure-cosmos/src/main/java/com/azure/cosmos/implementation/http/ReactorNettyClient.java). This creates compatibility issues when using CosmosDB in environments like Quarkus/GraalVM native image, where Vert.x is the preferred HTTP client.

Current situation:

  • azure-cosmos depends on azure-core-http-netty → reactor-netty
  • The HTTP client implementation is not pluggable
  • This differs from other Azure SDK components (Storage, Event Hubs, Key Vault, etc.) which support multiple HTTP client implementations

Describe the solution you'd like
Option 1 (preferred): support Vert.x HTTP Client

  • Allow CosmosDB to use azure-core-http-vertx as an alternative HTTP client implementation
  • This would align CosmosDB with other Azure SDK components and work seamlessly in Vert.x-based frameworks

Option 2: Make HTTP Client Implementation Pluggable
Similar to how other Azure SDK components work, allow users to choose between:

  • azure-core-http-netty (reactor-netty, current default)
  • azure-core-http-vertx (Vert.x)
  • others

Describe alternatives you've considered
keep using reactor-netty exclusively is not really ideal I think because forces non-reactor frameworks to include reactor-netty and graalVM native image compatibility issues

Additional context
The Apache Camel Quarkus project is currently working to add native support for the camel-azure-cosmosdb component, but the hardcoded reactor-netty dependency is blocking this effort.
We've noticed that other Azure SDK components—including Storage, Event Hubs, Service Bus, and Key Vault—already work seamlessly in Quarkus native mode because they support azure-core-http-vertx as an alternative HTTP client implementation. Having CosmosDB support the same pluggable HTTP client pattern would enable it to integrate smoothly with these frameworks and provide a consistent experience across all Azure services in cloud-native Java applications.

issue reference: https://github.com/apache/camel-quarkus/issues/2648

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日 18時間
マージ済み PR（30日）
206

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Azure/azure-sdk-for-java のほかの issue

Azure/azure-sdk-for-java の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。