[SERVER-31497] Move server-30084.js to sharding directory to prevent it from running in the sharded collections passthrough suite Created: 10/Oct/17  Updated: 30/Oct/23  Resolved: 17/Oct/17

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

Type: Bug Priority: Major - P3
Reporter: Nicholas Zolnierz Assignee: Nicholas Zolnierz
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-31582 Move sharding-specific aggregation te... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Query 2017-10-23
Participants:
Linked BF Score: 0

 Description   

This test uses the ShardingTest helper and thus should not be run against the aggregation_sharded_collections_passthrough suite.



 Comments   
Comment by Githook User [ 16/Oct/17 ]

Author:

{'email': 'nicholas.zolnierz@mongodb.com', 'name': 'Nick Zolnierz', 'username': 'nzolnierzmdb'}

Message: SERVER-31497: Move server-30084.js to sharding directory to prevent it from running in the sharded collections passthrough suite
Branch: master
https://github.com/mongodb/mongo/commit/d8279111b61afac242ddbb9f6d9697bbd14ed9d4

Comment by Max Hirschhorn [ 10/Oct/17 ]

nicholas.zolnierz, there are other tests in the jstests/aggregation/ directory that use the ShardingTest test fixture. I don't see anything in server30084.js that should care whether collections were being implicitly sharded or not. (It never actually calls DB.prototype.getCollection() as far as I can tell.)

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