[SERVER-57567] Update sharded passthrough suite to handle time series collections Created: 09/Jun/21  Updated: 29/Oct/23  Resolved: 21/Sep/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.4, 5.1.0-rc0

Type: New Feature Priority: Major - P3
Reporter: Arun Banala Assignee: Arun Banala
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on SERVER-59061 Shard does not block inserts into tim... Closed
Problem/Incident
Related
related to SERVER-59155 Enable some of the time-series tests ... Closed
is related to SERVER-55516 Remove tags for Time-series tests in ... Closed
is related to SERVER-59145 Enable secondary indexes on time-seri... Closed
is related to SERVER-59741 Enable more timeseries tests on shard... Closed
is related to SERVER-73024 Re-enable time-series sharded passthr... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: QE 2021-09-20, QE 2021-10-04
Participants:
Linked BF Score: 156

 Description   

This can be done by overriding DB.prototype.createCollection() if there is a time-series parameter. See implicitly_shard_accessed_collections.js for details on how this is being done for normal collections.



 Comments   
Comment by Githook User [ 19/Oct/21 ]

Author:

{'name': 'Arun Banala', 'email': 'arun.banala@mongodb.com', 'username': 'banarun'}

Message: SERVER-57567 Update sharded passthrough suite to handle time series collections

(cherry picked from commit 536cd38e7ab615181f5586519f60728c52e47108)

SERVER-57567 Fix bug to consider tests running on Windows

(cherry picked from commit 7ff8d8762cd47376e16f67e712a8f69d95d3689d)
Branch: v5.0
https://github.com/mongodb/mongo/commit/cb7881194dce4fa144b1a8bb742dfd0fe2700a42

Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 22/Sep/21 ]

Author:

{'name': 'Arun Banala', 'email': 'arun.banala@mongodb.com', 'username': 'banarun'}

Message: SERVER-57567 Fix bug to consider tests running on Windows
Branch: master
https://github.com/mongodb/mongo/commit/7ff8d8762cd47376e16f67e712a8f69d95d3689d

Comment by Githook User [ 21/Sep/21 ]

Author:

{'name': 'Arun Banala', 'email': 'arun.banala@mongodb.com', 'username': 'banarun'}

Message: SERVER-57567 Update sharded passthrough suite to handle time series collections
Branch: master
https://github.com/mongodb/mongo/commit/536cd38e7ab615181f5586519f60728c52e47108

Comment by Arun Banala [ 24/Aug/21 ]

The currently implementation of implicitly_shard_accessed_collections.js is to shard the collection with _id field on drop() operation. The time-series collections cannot be sharded on _id field. We need a time-series spec to shard the collection. So the proposal in this ticket is to use the time-series spec (if provided) in the createCollection() command for sharding.

Comment by David Percy [ 24/Aug/21 ]

Do we still need to do this, if we do SERVER-59164 and SERVER-59126? If I understand correctly:

  • SERVER-59126 makes sure the drop command also drops the buckets.
  • SERVER-59164 makes the shardCollection command shard the buckets.

So, whenever the passthrough suite implicitly calls drop or shardCollection on the view, it will succeed as if it were a normal collection?

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