-
Notifications
You must be signed in to change notification settings - Fork 946
Use collectionGroupReadTimeIndex for multi-tab synchronization #6073
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Size Report 1Affected Products
Test Logs |
Size Analysis Report 1This report is too large (343,385 characters) to be displayed here in a GitHub comment. Please use the below link to see the full report on Google Cloud Storage.Test Logs |
5d73d76
to
693250e
Compare
693250e
to
9898479
Compare
}); | ||
|
||
it('can get changes', async () => { | ||
it('cen get next documents from collection group with limit', async () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can
, and below
This drops one index created by #5988 and changes the multi-tab synchronization to use the collection group read time index. This works pretty well for normal query execution, but needs some adjusting to bundle loading as we don't know the collection groups of the bundles. As such, this PR adds functionality to the bundle loader to persist the names of the affected collection groups in LocalStoragel