Firebase.Firestore

Perform the aggregation on the server and download the result.

The result received from the server is presented, unaltered, without considering any local state. That is, documents in the local cache are not taken into consideration, neither are local modifications not yet synchronized with the server. Previously-downloaded results, if any, are not used. Every request using this source necessarily involves a round trip to the server.

The AggregateQuery will fail if the server cannot be reached, such as if the client is offline.

The operation was aborted, typically due to a concurrency issue like transaction aborts, etc.

Some document that we attempted to create already exists.

The operation was cancelled (typically by the caller).

Unrecoverable data loss or corruption.

Deadline expired before operation could complete.

For operations that change the state of the system, this error may be returned even if the operation has completed successfully. For example, a successful response from a server could have been delayed long enough for the deadline to expire.

Operation was rejected because the system is not in a state required for the operation's execution.

Internal errors.

Means some invariants expected by underlying system has been broken. If you see one of these errors, something is very broken.

Client specified an invalid argument.

Note that this differs from FailedPrecondition. InvalidArgument indicates arguments that are problematic regardless of the state of the system (e.g., an invalid field name).

Some requested document was not found.

The operation completed successfully.

Operation was attempted past the valid range.

The caller does not have permission to execute the specified operation.

Some resource has been exhausted, perhaps a per-user quota, or perhaps the entire file system is out of space.

The request does not have valid authentication credentials for the operation.

The service is currently unavailable.

This is a most likely a transient condition and may be corrected by retrying with a backoff.

Operation is not implemented or not supported/enabled.

Unknown error or an error from a different error domain.

Snapshot events will not be triggered by metadata-only changes.

Snapshot events will be triggered by any changes, including metadata-only changes.

Return local estimates for server timestamps that have not yet been set to their final value.

This estimate will likely differ from the final value and may cause these pending values to change once the server result becomes available.

Return null for server timestamps that have not yet been set to their final value.

Return the previous value for server timestamps that have not yet been set to their final value.

Causes Firestore to immediately return a value from the cache, ignoring the server completely (implying that the returned value may be stale with respect to the value on the server).

If there is no data in the cache to satisfy the DocumentReference.GetSnapshotAsync call will return an error and Query.GetSnapshotAsync will return an empty QuerySnapshot with no documents.

Causes Firestore to try to retrieve an up-to-date (server-retrieved) snapshot, but fall back to returning cached data if the server can't be reached.

Causes Firestore to avoid the cache, generating an error if the server cannot be reached.

Note that the cache will still be updated if the server request succeeds. Also note that latency-compensation still takes effect, so any pending write operations will be visible in the returned data (merged into the server-provided data).

Unknown properties are silently ignored.

Unknown properties cause an exception to be thrown.

Unknown properties cause a warning, but no error.