Update the integration test to verify that bloom filter averted full requery #11440
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…DetectDeletes to testResumingAQueryShouldUseBloomFilterToAvoidFullRequery
…rMismatchInfo::bloom_filter
google-oss-bot
added
api: abtesting
api: analytics
api: appcheck
api: appdistribution
api: auth
api: core
api: crashlytics
api: database
api: dynamiclinks
api: functions
api: inappmessaging
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update the integration test for the bloom filter to also verify that Watch specified a bloom filter that could be used to avert the full requery.
Googlers see b/274140502 for more details.
This PR is a port of firebase/firebase-js-sdk#7095, and its follow-up improvements in firebase/firebase-js-sdk#7112. The corresponding Android port is firebase/firebase-android-sdk#4768.
#no-changelog