[SERVER-53816] collection drop JS hooks in sharded collections passthrough suites incompatible with time-series tests Created: 14/Jan/21  Updated: 29/Oct/23  Resolved: 25/Jan/21

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

Type: Improvement Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2021-01-25
Participants:

 Description   

In the sharded collection jscore passthrough test suites, collection drops are overridden to recreate and shard the collection with the default options. Time-series tests require custom collection options for testing the time-series behavior, which makes these tests incompatible with the sharded collection passthrough hooks.

=== OLD DESCRIPTION =====

Time-series tests are currently excluded from the sharded jscore passthrough suites using the assumes_unsharded_collection test tag. It would be beneficial for test coverage to look into whether this restriction can be lifted.



 Comments   
Comment by Githook User [ 24/Jan/21 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-53816 time-series tests should be tagged with 'assumes_no_implicit_collection_creation_after_drop'

Time-series tests require custom collection creation options that are incompatible with the defaults
in the collection drop JS hook in sharded collection passthroughs.
Branch: master
https://github.com/mongodb/mongo/commit/72c083cee6c2e30d15b581808441bef06d276d6a

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