Merge pull request #1915 from firebase/next

release: January

Author: pr-Mais

.github/workflows/readmes-updated.yml

@@ -32,7 +32,7 @@ jobs:
       - name: Set up Node.js
         uses: actions/setup-node@v3
         with:
-          node-version: 16
+          node-version: 18
           cache: "npm"
           cache-dependency-path: "**/functions/package-lock.json"
 

.github/workflows/test.yml

@@ -2,18 +2,16 @@ name: Testing
 
 on:
   push:
-    branches:
-      - "**"
+    branches: [next]
   pull_request:
-    branches:
-      - "**"
+    branches: ["**"]
 
 jobs:
   nodejs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        node: ["14", "16"]
+        node: ["16", "18"]
     name: node.js_${{ matrix.node }}_test
     steps:
       - uses: actions/checkout@v3

.github/workflows/validate.yml

@@ -13,7 +13,7 @@ jobs:
       - name: Setup node
         uses: actions/setup-node@v3
         with:
-          node-version: 14
+          node-version: 18
       - name: NPM install
         run: SKIP_POSTINSTALL=yes npm i
       - name: Prettier Lint Check

delete-user-data/CHANGELOG.md

@@ -1,3 +1,7 @@
+## Version 0.1.20
+
+fix - update regex for RTDB instance param
+
 ## Version 0.1.19
 
 chore(delete-user-data): remove firebase-tools dependency

delete-user-data/README.md

@@ -43,7 +43,7 @@ For example, if you have the collections `users` and `admins`, and each collecti
 
 * Cloud Firestore delete mode: (Only applicable if you use the `Cloud Firestore paths` parameter.) How do you want to delete Cloud Firestore documents? To also delete documents in subcollections, set this parameter to `recursive`.
 
-* Realtime Database instance: From which Realtime Database instance do you want to delete data keyed on a user ID?
+* Realtime Database instance: What is the ID of the Realtime Database instance from which you want to delete user data (keyed on user ID)?
 
 
 * Realtime Database location: (Only applicable if you provided the `Realtime Database instance` parameter.) From which Realtime Database location do you want to delete data keyed on a user ID?

delete-user-data/extension.yaml

@@ -13,7 +13,7 @@
 # limitations under the License.
 
 name: delete-user-data
-version: 0.1.19
+version: 0.1.20
 specVersion: v1beta
 
 displayName: Delete User Data
@@ -116,11 +116,11 @@ params:
   - param: SELECTED_DATABASE_INSTANCE
     label: Realtime Database instance
     description: >
-      From which Realtime Database instance do you want to delete data keyed on a user ID?
+      What is the ID of the Realtime Database instance from which you want to delete user data (keyed on user ID)?
     type: string
     example: my-instance
-    validationRegex: ^([0-9a-z_.-]*)$
-    validationErrorMessage: Invalid database instance
+    validationRegex: ^[^\.\$\#\]\[\/\x00-\x1F\x7F]+$
+    validationErrorMessage: Invalid database instance. Make sure that you have entered just the instance ID, and not the entire database URL.
     required: false
 
   - param: SELECTED_DATABASE_LOCATION

docs/firestore-bigquery-export/Clustering.md

@@ -12,7 +12,7 @@ Through the extension, adding clustering is as simple as adding a comma-separate
 
 Clustering allows up to a maximum of four fields and can be configured similar to
 
-`document_id, timestamp, event_id, data`
+`document_id, document_name, timestamp, event_id, data`
 
 ![example](/docs/firestore-bigquery-export/media/clustering.png)
 

docs/firestore-bigquery-export/get-started.md

@@ -89,7 +89,7 @@ During installation, you will be prompted to specify a number of configuration p
 
   This parameter will allow you to set up Clustering for the BigQuery Table
   created by the extension. (for example: `data,document_id,timestamp`- no whitespaces). You can select up to 4 comma-separated fields(order matters).
-  Available schema extensions table fields for clustering: `document_id, timestamp, event_id, operation, data`.
+  Available schema extensions table fields for clustering: `document_id, document_name, timestamp, event_id, operation, data`.
 
 - **Backup Collection Name:**
 

firestore-bigquery-export/CHANGELOG.md

@@ -1,3 +1,8 @@
+## Version 0.1.44
+
+fix - apply the task queue configurations in `syncBigQuery` and set max attempts to 5
+fix - MAX_DISPATCHES_PER_SECOND is now set to take effect based on user's configuration
+
 ## Version 0.1.43
 
 fix - correctly partition when only "timestamp" is selected for partition options

firestore-bigquery-export/PREINSTALL.md

@@ -5,6 +5,8 @@ The extension creates and updates a [dataset](https://cloud.google.com/bigquery/
 - A [table](https://cloud.google.com/bigquery/docs/tables-intro) of raw data that stores a full change history of the documents within your collection. This table includes a number of metadata fields so that BigQuery can display the current state of your data. The principle metadata fields are `timestamp`, `document_name`, and the `operation` for the document change.
 - A [view](https://cloud.google.com/bigquery/docs/views-intro) which represents the current state of the data within your collection. It also shows a log of the latest `operation` for each document (`CREATE`, `UPDATE`, or `IMPORT`).
 
+*Warning*: A BigQuery table corresponding to your configuration will be automatically generated upon installing or updating this extension. Manual table creation may result in discrepancies with your configured settings.
+
 If you create, update, delete, or import a document in the specified collection, this extension sends that update to BigQuery. You can then run queries on this mirrored dataset.
 
 Note that this extension only listens for _document_ changes in the collection, but not changes in any _subcollection_. You can, though, install additional instances of this extension to specifically listen to a subcollection or other collections in your database. Or if you have the same subcollection across documents in a given collection, you can use `{wildcard}` notation to listen to all those subcollections (for example: `chats/{chatid}/posts`).