Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
GCP stateless HA support via Firestore and GCS #2821
This follows information in this issue and
Firestore must be configured for "Native" mode, which allows for document snapshotting.
Firestore automatically indexes all individual fields and requires custom indexes be created for compound queries. Both the Firestore Backend and Firestore Events "Backend/Handler" check, create, and block until indexes are created. This is done to prevent query errors on cluster startup.
Two composite indexes are required for the events collection:
One composite index is required for the cluster-data collection:
Firestore Doc IDs
Firestore Document IDs must be unique, cannot start with periods, and cannot contain forward
Both Firestore Event and Firestore Backend's support record purging; events are purged based on the created timestamp of the event as they're not updated, while records stored in the Firestore Backend are purged based on and only if they have
Firestore Backend watches collection and document snapshots and reports those to all watchers. Document added and modified events are pushed as