Skip to content

Allow remote updates from watch to heal a cache with synthesized deletes in it #1015

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

Merged
merged 14 commits into from
Jul 18, 2018
Merged
Show file tree
Hide file tree
Changes from 11 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 20 additions & 4 deletions packages/firestore/src/local/local_store.ts
Original file line number Diff line number Diff line change
Expand Up @@ -425,13 +425,27 @@ export class LocalStore {
const documentBuffer = new RemoteDocumentChangeBuffer(this.remoteDocuments);
return this.persistence.runTransaction('Apply remote event', txn => {
const promises = [] as Array<PersistencePromise<void>>;
let authoritativeUpdates = documentKeySet();
objUtils.forEachNumber(
remoteEvent.targetChanges,
(targetId: TargetId, change: TargetChange) => {
// Do not ref/unref unassigned targetIds - it may lead to leaks.
let queryData = this.targetIds[targetId];
if (!queryData) return;

// When a global snapshot contains updates (either add or modify) we
// can completely trust these updates as authoritative.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be worth adding, " and blindly apply them to our cache (as a defensive measure to promote self-healing in the unfortunate case that our cache is ever somehow corrupted / out-of-sync)." since in an ideal world I think this code would be unnecessary.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

//
// If the document is only updated while removing it from a target
// then watch isn't obligated to send the absolute latest version: it
// can send the first version that caused the document not to match.
change.addedDocuments.forEach(key => {
authoritativeUpdates = authoritativeUpdates.add(key);
});
change.modifiedDocuments.forEach(key => {
authoritativeUpdates = authoritativeUpdates.add(key);
});

promises.push(
this.queryCache
.removeMatchingKeys(txn, change.removedDocuments, targetId)
Expand Down Expand Up @@ -463,13 +477,15 @@ export class LocalStore {
changedDocKeys = changedDocKeys.add(key);
promises.push(
documentBuffer.getEntry(txn, key).next(existingDoc => {
// Make sure we don't apply an old document version to the remote
// cache, though we make an exception for SnapshotVersion.MIN which
// can happen for manufactured events (e.g. in the case of a limbo
// document resolution failing).
// If a document update isn't authoritative, make sure we don't
// apply an old document version to the remote cache. We make an
// exception for SnapshotVersion.MIN which can happen for
// manufactured events (e.g. in the case of a limbo document
// resolution failing).
if (
existingDoc == null ||
doc.version.isEqual(SnapshotVersion.MIN) ||
authoritativeUpdates.has(doc.key) ||
doc.version.compareTo(existingDoc.version) >= 0
) {
documentBuffer.addEntry(doc);
Expand Down
82 changes: 81 additions & 1 deletion packages/firestore/test/unit/specs/listen_spec.test.ts
Original file line number Diff line number Diff line change
Expand Up @@ -271,7 +271,10 @@ describeSpec('Listens:', [], () => {
// (the document falls out) and send us a snapshot that's ahead of
// docAv3 (which is already in our cache).
.userListens(visibleQuery, 'resume-token-1000')
.watchAcksFull(visibleQuery, 5000, docAv2)
.watchAcks(visibleQuery)
.watchSends({ removed: [visibleQuery] }, docAv2)
.watchCurrents(visibleQuery, 'resume-token-5000')
.watchSnapshots(5000)
.expectEvents(visibleQuery, { fromCache: false })
.userUnlistens(visibleQuery)
.watchRemoves(visibleQuery)
Expand All @@ -283,6 +286,83 @@ describeSpec('Listens:', [], () => {
);
});

specTest('Individual (deleted) documents cannot revert', [], () => {
const allQuery = Query.atPath(path('collection'));
const visibleQuery = Query.atPath(path('collection')).addFilter(
filter('visible', '==', true)
);
const docAv1 = doc('collection/a', 1000, { visible: true, v: 'v1000' });
const docAv2 = doc('collection/a', 2000, { visible: false, v: 'v2000' });
const docAv3 = deletedDoc('collection/a', 3000);

return (
spec()
// Disable GC so the cache persists across listens.
.withGCEnabled(false)
.userListens(visibleQuery)
.watchAcksFull(visibleQuery, 1000, docAv1)
.expectEvents(visibleQuery, { added: [docAv1] })
.userUnlistens(visibleQuery)
.watchRemoves(visibleQuery)
.userListens(allQuery)
.expectEvents(allQuery, { added: [docAv1], fromCache: true })
.watchAcks(allQuery)
.watchSends({ removed: [allQuery] }, docAv3)
.watchCurrents(allQuery, 'resume-token-4000')
.watchSnapshots(4000)
.expectEvents(allQuery, { removed: [docAv1], fromCache: false })
.userUnlistens(allQuery)
.watchRemoves(allQuery)
// Supposing we sent a resume token for visibleQuery, watch could catch
// us up to docAV2 since that's the last relevant change to the query
// (the document falls out) and send us a snapshot that's ahead of
// docAv3 (which is already in our cache).
.userListens(visibleQuery, 'resume-token-1000')
.watchAcks(visibleQuery)
.watchSends({ removed: [visibleQuery] }, docAv2)
.watchCurrents(visibleQuery, 'resume-token-5000')
.watchSnapshots(5000)
.expectEvents(visibleQuery, { fromCache: false })
.userUnlistens(visibleQuery)
.watchRemoves(visibleQuery)
// Listen to allQuery again and make sure we still get no docs.
.userListens(allQuery, 'resume-token-4000')
.watchAcksFull(allQuery, 6000)
.expectEvents(allQuery, { fromCache: false })
);
});

specTest('Deleted documents in cache are fixed', [], () => {
const allQuery = Query.atPath(path('collection'));
const docAv1 = doc('collection/a', 1000, { key: 'a' });
const docDeleted = deletedDoc('collection/a', 2000);

return (
spec()
// Presuppose an initial state where the remote document cache has a
// broken synthesized delete at a timestamp later than the true version
// of the document. This requires both adding and later removing the
// document in order to force the watch change aggregator to propagate
// the deletion.
.withGCEnabled(false)
.userListens(allQuery)
.watchAcksFull(allQuery, 1000, docAv1)
.expectEvents(allQuery, { added: [docAv1], fromCache: false })
.watchSends({ removed: [allQuery] }, docDeleted)
.watchSnapshots(2000, [allQuery], 'resume-token-2000')
.watchSnapshots(2000)
.expectEvents(allQuery, { removed: [docAv1], fromCache: false })
.userUnlistens(allQuery)
.watchRemoves(allQuery)

// Now when the client listens expect the cached NoDocument to be
// discarded because the global snapshot version exceeds what came before.
.userListens(allQuery, 'resume-token-2000')
.watchAcksFull(allQuery, 3000, docAv1)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry - wouldn't this send an existence filter with count of 1 and not send this document (since the resume token is newer than the document)?

It looks like a query with a single NoDocument associated has an document count of 1, and we will not reset the query (only verified by glancing through the code).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's probably true... It would either send us an existence filter, or it could send us a RESET and then the contents.

You could fix it by using a different query than allQuery above to generate the initial state we want (and then we wouldn't include an existence filter here). BUT in general this test is an invalid set of watch events since we're intentionally getting the cache into a bad state. So I'm not sure we care.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've changed this to use a separate setup query to sidestep the existence filter issue.

.expectEvents(allQuery, { added: [docAv1], fromCache: false })
);
});

specTest('Listens are reestablished after network disconnect', [], () => {
const expectRequestCount = requestCounts =>
requestCounts.addTarget + requestCounts.removeTarget;
Expand Down
3 changes: 3 additions & 0 deletions packages/firestore/test/unit/specs/spec_test_runner.ts
Original file line number Diff line number Diff line change
Expand Up @@ -443,6 +443,9 @@ abstract class TestRunner {
}

private doStep(step: SpecStep): Promise<void> {
// tslint:disable-next-line:no-console
console.log(' step: ' + JSON.stringify(step));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume this is intentional? It'll be pretty spammy during successful runs, but it does seem useful.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I add this every time there's a failure to help me understand where it failed. I didn't mean to let this through. Removed.


if ('userListen' in step) {
return this.doListen(step.userListen!);
} else if ('userUnlisten' in step) {
Expand Down