Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#49,155 3 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
azure, python
Ambito
api, backend, cloud, devtools

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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
Lingua principale
Python
Stelle
5.6k
Fork
3.4k
Merge medio
2g 3h
PR unite (30g)
206

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Azure/azure-sdk-for-python

Tutte le issue di Azure/azure-sdk-for-python

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.