🐛 firebase/firestore-bigquery-export: firestore extension doesn't support non-default database?

[vipin-wellsky]

[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: firebase/firestore-bigquery-export
• Extension version: 0.1.55

• Configuration values (redact info where appropriate):

[REQUIRED] Step 3: Describe the problem

Steps to reproduce:

I cannot see an option to set firebase extension to listen to firestore collection in a different DB than the (default) one. Please either provide a option or help with any workaround for the same.

Expected result

Actual result

[cabljac]

I've added the feature request label.

This is blocked until the extensions platform fully supports v2 functions I believe.

[adonistseriotis]

Linking to this issue #2072.
I have commented there a potential solution for this issue the same way Algolia is supporting non-default DBs.

[cabljac]

Interesting, can you confirm the algolia extension works properly with that param? We encountered issues when trying to do this before, e.g:

#2090 (comment)

[adonistseriotis]

Interesting, can you confirm the algolia extension works properly with that param? We encountered issues when trying to do this before, e.g:

#2090 (comment)

I can confirm it works with the default db. However, I can also run a test to see if it's working with another db. Will let you know Monday.

[tlloydukdev]

this is an important one for multi-tenant use-cases. right now also blocked by not being able to deploy Stream to BigQuery with multi-firestore architecture, so a +1 from me and will watch the issue

[dirkjbreeuwer]

Plus 1 here

[rummanext]

Plus 1+

[cabljac]

I will escalate this to the firebase team, but from what I understand when we tried to do this the algolia way we ran into the issue -

#2090 (comment)

If anyone has tested that algolia extension with a non-default firestore instance, please let me know

[cabljac]

Just as a further comment:

https://firebase.google.com/docs/functions/firestore-events?gen=1st

Cloud Functions (1st gen) prerequisites an existing "(default)" database in Firestore native mode. It does not support Cloud Firestore named databases or Datastore mode. Please use Cloud Functions (2nd gen) to configure events in such cases.

So this is blocked until the extension platform supports v2 firebase triggers, which is currently does not.

https://firebase.google.com/docs/extensions/publishers/functions

[cabljac]

So I investigated and escalated this to the Firebase team - v2 firestore triggers are supported and those docs are out of date!

I will do a test but this should be unblocked soon.