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

bigquery-firestore-export: clearing PARTITIONING_FIELD is blocked but the DTS API allows it

Abierto
  • ¿Algo no está bien?
#2,985 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
76/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
backend, data-engineering

Línea de trabajo

Empieza en functions/src/dts.ts, en la guardia de PARTITIONING_FIELD y su comentario, y luego compara la implementación de extensión upstream correspondiente heredada en el commit a34ba233. Reproduce el PATCH en un proyecto real en la ubicación us y verifica que borrar el campo tenga éxito y cambie una ejecución posterior; se considera terminado cuando ambas implementaciones permiten el valor vacío sin la constante de error obsoleta.

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

Descripción

bigquery-firestore-export refuses to clear PARTITIONING_FIELD, but the Data Transfer API allows it.

Setting PARTITIONING_FIELD and later clearing it fails the update with:

Cannot remove partitioning_field from an existing transfer config. The BigQuery Data Transfer API does not support clearing this parameter once it has been set. To change partitioning, you must create a new transfer config with the desired partitioning settings.

The API does support it. Creating a new transfer config is a costly workaround, since run history is stored under the old config ID and does not come with you.

Reproduction

Run against a real project, us location:

  1. Create a scheduled query with partitioning_field: created_at and destination template probe_{run_time|"%H%M%S"}. Two runs produced tables partitioned DAY (field: created_at).
  2. Clear it: PATCH /v1/{name}?updateMask=params with "partitioning_field": "". Returns 200, and a follow-up GET reads it back as "".
  3. Trigger another run. It carries partitioning_field: "", reaches SUCCEEDED, and reports no error.
  4. Compare the destination tables:
probe_152800   DAY (field: created_at)     <- partitioning set
probe_152909   DAY (field: created_at)     <- partitioning set
probe_153056   (none)                      <- after clearing

So the clear is accepted, persists, runs, and changes the output. It is not silently ignored and it does not fail.

The "you cannot un-partition an existing table" concern does not apply here: the destination template gives every run a new time-suffixed table, so nothing is mutated in place.

Where it comes from

The guard and its comment are in functions/src/dts.ts in the upstream extension:

// The BigQuery Data Transfer API does not support clearing this parameter
throw new Error(PARTITIONING_FIELD_REMOVAL_ERROR);

The kit inherited both in a34ba233. The kit and the extension differ only in what happens after the throw, so both are affected.

Suggested fix

Drop the guard and let an empty partitioning_field through the update mask, and remove PARTITIONING_FIELD_REMOVAL_ERROR along with the comment asserting the limitation. Worth confirming against the extension too, since the belief originated there.

Not verified: behaviour in locations other than us, and whether a destination table without a time-suffixed template behaves differently.

Lenguaje dominante
TypeScript
Estrellas
978
Forks
433
Merge medio
20 h 44 min
PR fusionados (30 d)
17

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 firebase/extensions

Todos los issues de firebase/extensions

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.