Skip to content
This repository has been archived by the owner on Jan 21, 2022. It is now read-only.

Inconsistent db clients behaviour #738

Open
georgi-lozev opened this issue Sep 19, 2017 · 1 comment
Open

Inconsistent db clients behaviour #738

georgi-lozev opened this issue Sep 19, 2017 · 1 comment

Comments

@georgi-lozev
Copy link
Contributor

georgi-lozev commented Sep 19, 2017

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.

@cf-gitbot
Copy link
Collaborator

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/151211940

The labels on this github issue will be updated when the story is started.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants