You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are having a hard time to understand the architecture of this extension and we would need some clarification.
The extension comes as 4 cloud functions.
The first one is fsexportbigquery and is triggered by Firestore events whenever a document get created/updated/deleted. All clear.
For the 3 other ones, which are Task Queues, the documentation says the following:
syncBigQuery: A task-triggered function that gets called on BigQuery sync
initBigQuerySync: Runs configuration for sycning with BigQuery
setupBigQuerySync: Runs configuration for sycning with BigQuery
Just reading the function names, it seems syncBigQuery is supposed to do the same job than fsexportbigquery. Is it really ? Also initBigQuerySync and setupBigQuerySync have the same description and same implementation. In what are they different ?
When we look at the metrics, the 3 previous ones are never being triggered/called. Which led us to ask the question here.
Can someone explain the intended design ? Perhaps the doc could benefit from it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
We are having a hard time to understand the architecture of this extension and we would need some clarification.
The extension comes as 4 cloud functions.
The first one is fsexportbigquery and is triggered by Firestore events whenever a document get created/updated/deleted. All clear.
For the 3 other ones, which are Task Queues, the documentation says the following:
Just reading the function names, it seems syncBigQuery is supposed to do the same job than fsexportbigquery. Is it really ? Also initBigQuerySync and setupBigQuerySync have the same description and same implementation. In what are they different ?
When we look at the metrics, the 3 previous ones are never being triggered/called. Which led us to ask the question here.
Can someone explain the intended design ? Perhaps the doc could benefit from it.
Beta Was this translation helpful? Give feedback.
All reactions