You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* fix: log data and old data on fail to enqueue (#2183)
* Update firestore-bigquery-export/extension.yaml
Co-authored-by: Mais Alheraki <mais.alheraki@gmail.com>
* Update firestore-bigquery-export/extension.yaml
* chore: update wording of new param (#2185)
---------
Co-authored-by: Mais Alheraki <mais.alheraki@gmail.com>
Copy file name to clipboardExpand all lines: firestore-bigquery-export/README.md
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -126,6 +126,8 @@ To install an extension, your project must be on the [Blaze (pay as you go) plan
126
126
127
127
* Collection path: What is the path of the collection that you would like to export? You may use `{wildcard}` notation to match a subcollection of all documents in a collection (for example: `chatrooms/{chatid}/posts`). Parent Firestore Document IDs from `{wildcards}` can be returned in `path_params` as a JSON formatted string.
128
128
129
+
* Enable logging failed exports: If enabled, the extension will log event exports that failed to enqueue to Cloud Logging, to mitigate data loss.
130
+
129
131
* Enable Wildcard Column field with Parent Firestore Document IDs: If enabled, creates a column containing a JSON object of all wildcard ids from a documents path.
130
132
131
133
* Dataset ID: What ID would you like to use for your BigQuery dataset? This extension will create the dataset, if it doesn't already exist.
0 commit comments