[CDRIVER-2995] Failing aggregate-out unit test with write concern Created: 06/Mar/19 Updated: 28/Oct/23 Resolved: 07/Mar/19 |
|
| Status: | Closed |
| Project: | C Driver |
| Component/s: | libmongoc |
| Affects Version/s: | 1.14.0 |
| Fix Version/s: | 1.15.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Amy Giersch | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
AIX/gcc |
||
| Issue Links: |
|
||||||||
| Description |
|
Unit test /crud/read/aggregate-out fails when a write concern is in the connection string for the 2nd test with batchSize = 0. Since batchSize = 0 get back a cursor after the aggregate command, a getMore is sent and getMore contains the write concern. Looks like this will be fixed by the changes for "results": [ }, { "$match" : { "_id" : { "$gt" : 1 } } }, { "$out" : "other_test_collection" } ], "batchSize" : 0 } } Command getMore started: { "getMore" : 5371882048943694072, "collection" : "test", "writeConcern" : \{ "w" : "majority", "j" : true }, "$db" : "test", "lsid" : { "id" : { "$binary" : { "base64": "sAS3DPNiTS6ApKYrrupusQ==", "subType" : "04" }} }, "$clusterTime" : { "clusterTime" : { "$timestamp" : { "t" : 1551826988, "i" : 16 }}, "signature" : { "hash" : { "$binary" : { "base64": "AAAAAAAAAAAAAAAAAAAAAAAAAAA=", "subType" : "00" } }, "keyId" : 0 } } |
| Comments |
| Comment by Kevin Albertson [ 07/Mar/19 ] |
|
Hi Amy, thanks for the detailed report! As you predicted, this is resolved in To double check, I reproduced your test failure locally by running test-libmongoc with MONGOC_TEST_URI of mongodb://localhost:27017/db?w=1 before the changes of |