You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 21, 2022. It is now read-only.
It seems that there is inconsistent behavior of both db clients in allDocs with specified list of keys.
Here is sample unit test which exposes that mismatch.
The problem seems to be in the mongoclient.
For example if you query for documents with ids [1, 2, 3] in one partition and match only docs 1 and 3 you get [{doc1}, undefined, {doc3}] as a result. However if doc 2 is in different partition you get [{doc1}, {error:'not_found'}, {doc2}], which is the same as the behaviour of the couchclient in all cases for the same query string.
The text was updated successfully, but these errors were encountered:
It seems that there is inconsistent behavior of both db clients in
allDocs
with specified list of keys.Here is sample unit test which exposes that mismatch.
The problem seems to be in the mongoclient.
For example if you query for documents with ids
[1, 2, 3]
in one partition and match only docs1
and3
you get[{doc1}, undefined, {doc3}]
as a result. However if doc2
is in different partition you get[{doc1}, {error:'not_found'}, {doc2}]
, which is the same as the behaviour of the couchclient in all cases for the same query string.The text was updated successfully, but these errors were encountered: