fix(firestore-bigquery-export): remove multiple database support #2122
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cabljac
force-pushed
the
@invertase/rollback_multi-db
branch
from
bec1a03 to
3c3296d
Compare
|
When will you be supporting multi-db?? |
|
i need too supporting multi-db :( |
|
any chance to get it fix or any other workaround to support multi DB? |
|
1+ here |
|
still waiting for this, is so basic to use the extension |
|
Would love to use this extension as well but can't due to my data not being in default. Would also recommend updating the docs to be explicit that default db will be used. |
|
I will escalate this to the team, we're blocked from a platform side at the moment, as v1 functions dont support non-default db, and extensions don't support v2 for firestore triggers. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
should fix #2090