Skip to content

Commit 3b893bb

Browse files
committed
chore(firestore-bigquery-export): update README and CHANGELOG
1 parent e5b17ce commit 3b893bb

File tree

2 files changed

+1
-5
lines changed

2 files changed

+1
-5
lines changed

firestore-bigquery-export/CHANGELOG.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
## Version 0.1.56
22

3-
feat - improve sync strategy
3+
feat - improve sync strategy by immediately writing to BQ
44

55
## Version 0.1.55
66

firestore-bigquery-export/README.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -126,8 +126,6 @@ To install an extension, your project must be on the [Blaze (pay as you go) plan
126126

127127
* 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.
128128

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-
131129
* 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.
132130

133131
* 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.
@@ -191,5 +189,3 @@ This extension will operate with the following project IAM roles:
191189
* bigquery.dataEditor (Reason: Allows the extension to configure and export data into BigQuery.)
192190

193191
* datastore.user (Reason: Allows the extension to write updates to the database.)
194-
195-
* storage.objectAdmin (Reason: Allows the extension to create objects in the storage bucket.)

0 commit comments

Comments
 (0)