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

🐛 [firestore-bigquery-export] multi-db selection isn't working for Firestore triggers #2090

Closed
pr-Mais opened this issue May 10, 2024 · 1 comment · Fixed by #2122
Closed
Assignees
Labels
extension: firestore-bigquery-export Related to firestore-bigquery-export extension type: bug Something isn't working

Comments

@pr-Mais
Copy link
Member

pr-Mais commented May 10, 2024

[REQUIRED] Step 3: Describe the problem

The current version of the Stream Firestore to BigQuery extension allows specifying a secondary project for the Firestore triggers, however this doesn't work as the triggers are all 1st gen. Need to remove the feature.

See #2072

@titan-graham
Copy link

Found this issue via (#2072):

We are somewhat confused/bemused that the current version of the extension allows a non (default) database ID, but a non default database ID is not supported by the underlying technology (gen1 functions) that the extension relies on.

Error creating trigger: The request was invalid: generic::invalid_argument: source filter must follow '//firestore.googleapis.com/projects/{projectId}/databases/(default)'.

We've wasted pointless hours on this where in fact the extension as published simply cannot work in the way it's advertised. How is it possible this feature even made it into a release?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
extension: firestore-bigquery-export Related to firestore-bigquery-export extension type: bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants