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

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

Abierto
  • ¿Algo no está bien?
#49,166 1 comentario 1 reacción 4 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@pjohari-ms ya está trabajando en esto.

Desde el 8/8/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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
Lenguaje dominante
Java
Estrellas
2.6k
Forks
2.2k
Merge medio
1 d 22 h
PR fusionados (30 d)
225

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.