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

Allow newer Azure Storage SDKs in azure-kusto-ingest

Abierto
  • ¿Algo no está bien?
#652 0 comentarios 0 reacciones 0 asignados Ver en GitHub

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
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
azure, python
Área
backend, cloud

Línea de trabajo

Start with azure-kusto-ingest/pyproject.toml and the Queue and Blob client construction in azure/kusto/ingest/ingest_client.py. Review the linked Azure SDK discussion, determine which service API version the managed ingestion storage accounts support, and test queued ingestion with newer Storage SDKs. Done means compatibility is established and the dependency constraints or client configuration can be changed safely if supported.

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

Descripción

Codex for Tamir:

I’m upgrading an environment from Kusto Data and Ingest 5.0.1 to 6.0.4. It already uses Azure Storage Blob 12.28.0 and Queue 12.15.0, and I expected to keep those versions during the Kusto upgrade. But Ingest 6.0.4 requires Blob 12.26.0 and Queue 12.13.0 exactly, so those requirements are incompatible with the installed Storage versions.

I traced the exact pins to 51d8968a6, introduced in #574 after newer Storage SDKs began requesting an API version that was not yet available everywhere. The linked Azure SDK discussion describes the partial service rollout, and its last substantive update still mentions one lagging scale unit.

Kusto creates its Queue client and Blob client without an explicit api_version, so it relies on the SDK defaults. Are the exact package pins still needed? If Kusto-managed ingestion storage accounts still require an older service API, could these clients select that API version explicitly and allow applications to upgrade the Blob and Queue packages independently?

I have not tested live queued ingestion with the newer Storage SDKs. Before preparing a change, I’d like to understand whether the service limitation still exists and which API version these accounts support.

Lenguaje dominante
Python
Estrellas
204
Forks
119
Merge medio
2 h 8 min
PR fusionados (30 d)
1

Preparar el entorno

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

Todos los issues de Azure/azure-kusto-python

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.