bigquery-firestore-export - unable to create transferConfig

[sjerzak]

[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: _bigquery-firestore-export
• Extension version: _0.1.4

[REQUIRED] Step 3: Describe the problem

Extension is unable to create transferConfig

Steps to reproduce:

Install and config extension. It will stuck on

Expected result

TransferConfig created.

Actual result

Hang on "Creating a new transfer config and scheduling the query." status.

[jauntybrain]

Hi @sjerzak, thank you for reporting this issue. I am working on reproducing it but I need a bit more information.

Could you please verify if the Firestore collection that you specified during extension installation (defaults to transferConfigs) contains a document with a field name? If it does, could you please share the value of that field?

[sjerzak]

Hi

Thanks for checking on this.

I did some more checks and it seems that the issue occurs when I'm trying to use collection that already exists.
I've change extension settings back to use default transferConfigs collection and extension was able to create that collection with proper document containing fields (name etc...), then TransferConfig was created properly.

Answering your question I wasn't able to find document with a field name in collection specified by me before reverting to transferConfigs collection.

[jauntybrain]

@sjerzak thanks for the information! Yes, the specified collection must either be empty or contain a previously used transfer config, since it should only contain information about BigQuery transfers. We will make sure to highlight this in the documentation.

[sjerzak]

Could you please double check if "or contain a previously used transfer config" functionality is working correctly?
I reconfigured extension using transferConfigs collection, only thing I did change was Function memory(Optional) and it stuck on ext-bigquery-firestore-export-upsertTransferConfig again.

After deleting Firebase collection transferConfigs and manually removing BQ Data transfers extension worked as expected.
BQ Data transfers was added and Firestore collection transferConfigs were created.

[jauntybrain]

@sjerzak thanks for reporting this! I made a PR that resolves this issue.