The total count of documents that match
target_id.
If different from the count of documents in the client that match, the
client must manually determine which documents no longer match the target.
A bloom filter that contains the UTF-8 byte encodings of the resource names
of the documents that match
target_id, in the form
projects/{project_id}/databases/{database_id}/documents/{document_path}
that have NOT changed since the query results indicated by the resume token
or timestamp given in Target.resume_type.
This bloom filter may be omitted at the server's discretion, such as if it
is deemed that the client will not make use of it or if it is too
computationally expensive to calculate or transmit. Clients must gracefully
handle this field being absent by falling back to the logic used before
this field existed; that is, re-add the target without a resume token to
figure out which documents in the client's cache are out of sync.
A bloom filter that contains the UTF-8 byte encodings of the resource names
of the documents that match
target_id, in the form
projects/{project_id}/databases/{database_id}/documents/{document_path}
that have NOT changed since the query results indicated by the resume token
or timestamp given in Target.resume_type.
This bloom filter may be omitted at the server's discretion, such as if it
is deemed that the client will not make use of it or if it is too
computationally expensive to calculate or transmit. Clients must gracefully
handle this field being absent by falling back to the logic used before
this field existed; that is, re-add the target without a resume token to
figure out which documents in the client's cache are out of sync.
A bloom filter that contains the UTF-8 byte encodings of the resource names
of the documents that match
target_id, in the form
projects/{project_id}/databases/{database_id}/documents/{document_path}
that have NOT changed since the query results indicated by the resume token
or timestamp given in Target.resume_type.
This bloom filter may be omitted at the server's discretion, such as if it
is deemed that the client will not make use of it or if it is too
computationally expensive to calculate or transmit. Clients must gracefully
handle this field being absent by falling back to the logic used before
this field existed; that is, re-add the target without a resume token to
figure out which documents in the client's cache are out of sync.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-01-27 UTC."],[],[]]
