extensions icon indicating copy to clipboard operation
extensions copied to clipboard

[firestore-bigquery-export] Add transform function url parameter to import script

Open jsnee opened this issue 3 years ago • 7 comments

[REQUIRED] Step 2: Extension name

This feature request is for extension: firestore-bigquery-export

What feature would you like to see?

I'd like to see the import script have an option to provide a URL to a transform function, similar to the way the exporter itself works.

How would you use it?

This would be used to transform the data making the same call as is made in the exporter itself. Currently, the records imported with the import script do not match the records processed by the exporter if the exporter utilizes a transform function. Adding this feature would preserve parity between imported and exported records.

jsnee avatar Oct 12 '22 15:10 jsnee

+1 to this. Not having the ability to transform data makes the exporter a bit useless for data that requires the transformations @cabljac

50an6xy06r6n avatar Mar 29 '23 06:03 50an6xy06r6n

This is very much needed. If the extension has a transform url the import script is basically doing half of the work and futher transformation is necessary.

toturx avatar Apr 10 '23 15:04 toturx

+1. will be very helpful to have this feature 🙏.

Mr-Goldberg avatar Sep 01 '23 19:09 Mr-Goldberg

Another request for this feature. It would be very much appreciated!

oscarhinde avatar Nov 15 '23 15:11 oscarhinde

Currently there is a parameter for this functionality, but it sounds like it isn't enabled or working currently, I will investigate

https://github.com/firebase/extensions/pull/849

cabljac avatar Nov 23 '23 12:11 cabljac

Another request for this feature please.
Additionally, from the documentation there is nothing informing the user that this functionality does NOT work (as one can select yes for import existing records and provide a transform function URL without being told it will not be triggered on import). The user simply has to find out through trial and error. Although the functionality itself would be wonderful, in the mean time, if documentation could be updated to inform the user transform functions aren't triggered on import, it would be a (hopefully) small effort than could save other users from time spent figuring it out via trial and error.

sorrel-certifyos avatar Mar 07 '24 21:03 sorrel-certifyos