[SERVER-33007] lte assertion in distinct_compound_index.js is in the wrong order Created: 30/Jan/18  Updated: 30/Jan/18  Resolved: 30/Jan/18

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Charlie Swanson Assignee: Charlie Swanson
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-33006 lte assertion in distinct_compound_in... Closed
Operating System: ALL
Sprint: Query 2018-02-12
Participants:

 Description   

When we introduced the 2-shards sharded collections passthrough, this assertion was typed in the wrong order:

   // If the collection is sharded, we expect at most 2 distinct values per shard. If the
   // collection is not sharded, we expect 2 returned.
   assert.lte(2 * FixtureHelpers.numberOfShardsForCollection(coll),
              explain_distinct_with_query.executionStats.nReturned);

That should be flipped:

   // If the collection is sharded, we expect at most 2 distinct values per shard. If the
   // collection is not sharded, we expect 2 returned.
   assert.lte(explain_distinct_with_query.executionStats.nReturned,
              2 * FixtureHelpers.numberOfShardsForCollection(coll));



 Comments   
Comment by Charlie Swanson [ 30/Jan/18 ]

Somehow filed this twice. Closing this one as a duplicate.

Generated at Thu Feb 08 04:31:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.