Hey, I'm currently upgrading my Firebase extension...
# community-help
j
Hey, I'm currently upgrading my Firebase extensions to the new version, and I encounter an issue that I believe others will run into as well: Since I cannot change the "Firestore Database region" from "nam5 (US multi-region)" to the Europe one, but my data is in Europe, I need to deinstall and reinstall the extension. Could this be fixed by allowing the user to change the "Firestore Database region" when upgrading from certain versions?
j
That's unfortunately a Firebase UI limitation we don't have control over
I'd recommend posting in their user-groups to point this out
j
The intersting thing is that I was able to set it when updating my Firestore to BigQuery extensions
It is now also blocked but I was able to set it when i did the update just now
It was empty though while in the Typesense one, it was already prefilled with nam5
f
The default parameter hasn't got to do with if the parameter is immutable or not, we just provide a default. From what I can see on their
exension.yaml
, they haven't marked their database region parameter as immutable, while we have. We can test updating it to be mutable if @Jason Bosco wants to
j
you're right, it is possible to change it
Does it impact the way the Typesense extension works?
j
Hmmm, I vaguely remember reading that the region has to immutable somewhere in their docs... But I'm down to trying it
j
Since its a new field, what would happen if you just change the default parameter to null?
But somehow make it required 😅
I guess it would still have to be mutable
j
There was a very specific set of options that worked with those two fields and it took a bunch of trial and error to figure out what we have now (search for location on this page: https://github.com/typesense/firestore-typesense-search/commits/master/) 😅 I wouldn't be surprised if we run into more gotchas
j
I think we need to differentiate between the function region and the database region.
I think you played around with the function regions
As Fanis mentioned, in the Firestore to BigQuery extension its like this. They don't have a default value.
Copy code
required: true
immutable: false
j
Strange, they don't even set
COLLECTION_PATH
to be immutable
Ok, we can try mimicing those settings
@Fanis Tharropoulos Could you do a PR and then an RC build?
j
Let me know once its done, I'm happy to test. I can fix it quickly if something goes wrong.
Worst case I will have to set it again up anyways 😆
j
j
Is it possible to update to this rc build?
f
j
Because if I can only install it, it won't solve my issue 😆
f
You sadly can't (AFAIK) update to an rc build, you can only re-install it
j
When you click on "Update" does it take you to a new page where the URL has the version as a query param by any chance?
If so, I wonder if you can switch the version manually in that update link
j
It looks like it worked to change the version
This looks good
Its installing
It went through
ty 👍
j
Nice!
Thank you for helping catch this nuance
🙌 1
Submitted this version to Firebase for review. Typically takes 3-5 days for them to publish it
🙌 1
The new version is now live on Extensions Hub
@Janick Fischer Could you try updating from within the update prompt you should now see on old versions of the extension?
j
Looks good so far 👍
Worked like a charm, thank you both for the incredible fast solution 😄
🙌 2
j
Awesome, thank you for confirming!