Skip to content

Conversation

cabljac
Copy link
Contributor

@cabljac cabljac commented Nov 14, 2023

This is to replace the PR here as refactors have made the original fork diverge too much from next. Need to re-review before we merge.

Should fix #1688

@jwerner08
Copy link
Contributor

Hey @cabljac, Just wanted to share my thanks and appreciation for helping out here! :)

@janssen92
Copy link

You could use the PROJECT_ID as a fallback if no big query project id is provided to be downward compatible

@Naihell
Copy link

Naihell commented Dec 6, 2023

Hey there! Any news about this one? I've tested using 0.1.43 extension version, following @jwerner08's instructions, but for some reason BigQuery project Id was always being setted to "undefined". On the other way, if I manually overwrite project variables, everything runs perfectly.

Having this functionality in a production branch would be amazing, it's quite easy to use and most of my jobs runs on cross projects.

Thanks for the excellent work!

@jauntybrain jauntybrain self-assigned this Jan 12, 2024
@jauntybrain jauntybrain changed the title feat: add gcp project as parameter in import script feat(firestore-bigquery-export): support cross-project import with the import script Jan 15, 2024
@pr-Mais
Copy link
Member

pr-Mais commented Jan 24, 2024

@jauntybrain can you resolve the conflict

@cabljac cabljac merged commit 77a3559 into next Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

🐛 [firestore-bigquery-export] Cross Project Import Script

6 participants