🐛 [firestore-bigquery-export] Custom event handler for onSuccess not called
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
- 48/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Tranquilo
- Stack tecnológico
- typescript
Línea de trabajo
Comienza con la ruta de publicación de eventos personalizados de la extensión firestore-bigquery-export y compárala con la configuración proporcionada del canal, la región y el tipo de evento de Eventarc. Reproduce la configuración usando la configuración documentada y el handler de TypeScript; después, inspecciona los logs de la extensión y de Eventarc. Se considera completado cuando una sincronización correcta de BigQuery publica onSuccess y el handler se ejecuta con los datos del evento.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
[READ] Step 1: Are you in the right place?
Issues filed here should be about bugs for a specific extension in this repository.
If you have a general question, need help debugging, or fall into some
other category use one of these other channels:
- For general technical questions, post a question on StackOverflow
with the firebase tag. - For general Firebase discussion, use the firebase-talk
google group. - To file a bug against the Firebase Extensions platform, or for an issue affecting multiple extensions, please reach out to
Firebase support directly.
[REQUIRED] Step 2: Describe your configuration
- Extension name: [firestore-bigquery-export]
- Extension version: firebase/[email protected]
- Configuration values (redact info where appropriate):
ALLOWED_EVENT_TYPES=firebase.extensions.firestore-counter.v1.onSuccess
BIGQUERY_PROJECT_ID=${param:PROJECT_ID}
COLLECTION_PATH=recipes
DATASET_ID=recipes_dataset_export_raw
DATASET_LOCATION=europe-west3
EVENTARC_CHANNEL=projects/my-xxx/locations/us-central1/channels/firebase
EXCLUDE_OLD_DATA=no
LOG_FAILED_EXPORTS=no
MAX_DISPATCHES_PER_SECOND=100
TABLE_ID=recipes_table_export_raw
TABLE_PARTITIONING=NONE
TIME_PARTITIONING_FIELD_TYPE=omit
USE_COLLECTION_GROUP_QUERY=no
USE_NEW_SNAPSHOT_QUERY_SYNTAX=yes
WILDCARD_IDS=false
[REQUIRED] Step 3: Describe the problem
I've setup firestore-bigquery-export to raise the event firebase.extensions.firestore-counter.v1.onSuccess. Whats quite odd is that in the 'Extension configuration' view of the extension instance the description of this event is 'Occurs when image resizing completes successfully. The event will contain further details about specific formats and sizes.'. Seems to be a copy/paste from the other extension ;)
I implemented and deployed a custom event handler as firebase v2 function and deployed it in the same firebase project (region of the function us-central1). The actual sync of the firebase data into BigQuery works fine. However, my event handler for onSuccess is never executed and I also cannot confirm that the event is even raised (because I can't find any logs about it).
In GC console unter Eventarc I see that the channel and trigger have been created with the correct with the correct destination. Trigger and channel are both in region us-central1.
Steps to reproduce:
Setup a Firebase project with a firestore collection in europe-west3 and install the firestore-bigquery-export extension with mentioned config.
Deploy the following firebase function as event handler.
import eventarc = require('firebase-functions/v2/eventarc')
import logger = require('firebase-functions/logger')
exports.onBigQuerySyncSuccess = eventarc.onCustomEventPublished(
{
eventType: 'firebase.extensions.firestore-counter.v1.onSuccess',
channel: projects/${firebaseFunctionsParams.projectID}/locations/us-central1/channels/firebase,
region: 'us-central1',
},
(event) => {
logger.info('handled firebase.extensions.firestore-counter.v1.onSuccess; received data', event)
return Promise.resolve()
})
Expected result
When changing a document in the collection it is syned into BigQuery and afterward the event handler onBigQuerySyncSuccess is executed.
Actual result
Sync into BigQuery works, event handler is not executed. Somehow I have the impression that the event isn't even raised.
In the GC logs there is a log entry for ext-firestore-bigquery-export-fsexportbigquery with description "Initializing extension with configuration". The "jsonPayload" does not include eventarc channel like in the extensions config data:
jsonPayload: {
bqProjectId: "my-xxx"
clustering: null
collectionPath: "recipes"
databaseId: "(default)"
datasetId: "recipes_dataset_export_raw"
datasetLocation: "europe-west3"
doBackfill: false
docsPerBackfill: 200
excludeOldData: false
initialized: false
instanceId: "firestore-bigquery-export"
location: "us-central1"
logFailedExportData: false
maxDispatchesPerSecond: 100
message: "Initializing extension with configuration"
tableId: "recipes_table_export_raw"
timePartitioning: null
useCollectionGroupQuery: false
useNewSnapshotQuerySyntax: true
wildcardIds: false
}
Thanks,
Max
- Lenguaje dominante
- TypeScript
- Estrellas
- 978
- Forks
- 433
- Merge medio
- 20 h 44 min
- PR fusionados (30 d)
- 17
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de firebase/extensions
-
decision(storage-resize-images): kit/extension parity – ALLOWED_EVENT_TYPES is ignored, the kit reads EXT_SELECTED_EVENTSPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertodecision kits
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
firebase/extensions#3273 ·
Los mantenedores suelen responder en 1 día
-
docs(storage-resize-images): kit README's Multiple instances section fails in an installed projectAbiertokits type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
firebase/extensions#3271 ·
Los mantenedores suelen responder en 1 día
-
kits type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
firebase/extensions#3270 ·
Los mantenedores suelen responder en 1 día
-
fix(storage-resize-images): kit/extension parity – BUCKET_REGION offers europe-north2 and northamerica-south1, which can't deployPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertokits type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
firebase/extensions#3268 ·
Los mantenedores suelen responder en 1 día
-
fix(storage-resize-images): kit/extension parity – onCompletion event no longer carries the object namePosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertokits type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
firebase/extensions#3266 ·
Los mantenedores suelen responder en 1 día
Todos los issues de firebase/extensions
Issues similares
-
agent/scanner help wanted hive/claimed-by-scanner kind/bug stage/020-claimed
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
hivecommons/rationguard#315 ·
Los mantenedores suelen responder en 1 día
-
agent-ready area: ui-sdk priority: p3 type: chore
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
schlessera/brain-kit#2534 ·
Los mantenedores suelen responder en 1 día
-
bug lane:gh-5
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
LLM-4-People/bridlewise-testing#122 ·
Los mantenedores suelen responder en 1 día
-
bug priority: P2
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
enhancement priority:low ready-for-dev
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
Los mantenedores suelen responder en 1 día