🐛 [firestore-bigquery-export] Configure Firestore events that trigger the export

[mmiro1]

[READ] Step 1: Are you in the right place?

I think so. It is a change to the firestore-bigquery-export extension.

[REQUIRED] Step 2: Extension name

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

What feature would you like to see?

I would like to be able to mark certain Firestore events to be ignored by the export function. For example, being able to disable exports for Deletes operations, and not transferring those to BigQuery. Don't get me wrong, I still think all operations should be enabled by default, but having that extra configuration would help.

How would you use it?

In my case, and I suppose that other too, I have a TTL (time-to-live) configured on the exporting collection, since it increases a lot over time and I don't need all the data after X days, but I would like to maintain it on BigQuery for more time.
When deleting these documents, I don't need to notify BigQuery of these changes, which would decrease resources needed and costs (logs, storage, bandwidth, ...).

[mmiro1]

I have been looking at the function code and I think I could open a PR with the change.
By modifying the file firestore-bigquery-export/functions/src/index.ts::166 and adding a check could work, and modifying the file firestore-bigquery-export/functions/src/config.ts accordingly. But I don't know how this reflects in the Firestore UI config panel. Please let me know if you think this could be useful and if you would like me to open a PR.

[cabljac]

Hi, thanks for raising this! It's being tracked, we'll provide updates when available.

We'll investigate your suggestion, we're always open to community PRs, they're great!

Our release process is blocked right now but as soon as it's fixed we can look into maybe adding this.