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
* Performing an update on a Datastore mode database could silently change it to Firestore Native
* Enabling PITR (--point-in-time-recovery=ENABLED) while not specifying --disaster-recovery=ENABLED
would silently disable disaster recovery, and vice-versa
The former issue was due to always sending FIRESTORE_NATIVE as the database type, when we
actually didn't need to send it at all. The latter issue was due to command-line option
parsing that assumed not specifying an option was equivalent to sending an explicit DISABLE.
0 commit comments