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

[azure-search-documents] Enable HTTPX async transport for AnyIO/Trio callers

Abierto
  • ¿Algo no está bien?
#49,155 3 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
azure, python
Área
api, backend, cloud, devtools

Línea de trabajo

The issue involves modifying the async HTTP transport layer in azure-core to support HTTPX for Trio compatibility. Start by examining the existing async client pipeline in azure/search/documents/aio/_client.py and the related azure-core issue #41382. Understand how transports are configured and swapped. The acceptance test requires running representative async Search/index operations under both asyncio and Trio backends via anyio.run. Focus on ensuring transport ownership and cleanup work correctly with both credential types.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Client customer-reported needs-team-attention question Search Service Attention
Motivation

Microsoft Agent Framework is exploring AnyIO support so its Python agents can run with either asyncio or Trio. Its Azure AI Search integration uses azure.search.documents.aio.SearchClient and azure.search.documents.indexes.aio.SearchIndexClient (and, when available, the async knowledge-base retrieval client). These clients depend on azure-core; the default azure-core async HTTP transport uses aiohttp, which is asyncio-specific. Agent Framework currently lists aiohttp explicitly for this integration as a consequence. HTTPX's async client supports both asyncio and Trio.

Request

Please provide a supported, documented HTTPX async transport for azure-search-documents, rather than requiring the aiohttp transport to use its async clients. If changing the azure-core async default from aiohttp to HTTPX is acceptable, that would address this; otherwise a stable azure-core HTTPX transport option that can be selected without bringing in aiohttp would suffice. Please include the async Search, index-management, and knowledge-base paths, plus credentials/transport ownership and cleanup, in the backend-compatibility assessment.

The useful acceptance check is the same representative async Search/index operation run under anyio.run(main, backend="asyncio") and anyio.run(main, backend="trio") with no asyncio-only transport in the Trio path (both key-based and async token credentials where supported). This is a request for end-to-end support, not an assertion that substituting one HTTP client alone makes every SDK layer Trio-compatible.

Related work and references
Lenguaje dominante
Python
Estrellas
5.6k
Forks
3.4k
Merge medio
1 d 18 h
PR fusionados (30 d)
214

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-python

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

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.