Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 firebase/firestore-bigquery-export: firestore extension doesn't support database? #2211

Open
vipin-wellsky opened this issue Nov 6, 2024 · 6 comments
Labels
blocked Blocked by an outstanding issue or PR type: feature request New feature or request

Comments

@vipin-wellsky
Copy link

vipin-wellsky commented Nov 6, 2024

[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
@vipin-wellsky vipin-wellsky added the type: bug Something isn't working label Nov 6, 2024
@vipin-wellsky vipin-wellsky changed the title 🐛 firebase/firestore-bigquery-export: firestore extension doesn 🐛 firebase/firestore-bigquery-export: firestore extension doesn't support database? Nov 6, 2024
@cabljac cabljac added type: feature request New feature or request and removed type: bug Something isn't working labels Nov 13, 2024
@cabljac
Copy link
Contributor

cabljac commented Nov 13, 2024

I've added the feature request label.

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

@cabljac cabljac added the blocked Blocked by an outstanding issue or PR label Nov 13, 2024
@adonistseriotis
Copy link

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
Copy link
Contributor

cabljac commented Nov 15, 2024

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
Copy link

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
Copy link

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
Copy link

Plus 1 here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Blocked by an outstanding issue or PR type: feature request New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants