[DOCS-14633] Update renameCollection public documentation Created: 08/Jul/21  Updated: 30/Oct/23  Due: 12/Jul/21  Resolved: 13/Jul/21

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: 5.0 Required
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Alison Huh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to DOCS-13880 Source and target database primary sh... Closed
Participants:
Days since reply: 2 years, 30 weeks, 2 days ago
Epic Link: DOCSP-9747

 Description   

Review/adapt the renameCollection documentation:

  • Sharded collections: specify that rename for sharded collections is now allowed (but not between different DBs)
  • Resource Locking: this section is currently just valid for plain replica sets
  • Exceptions: all the currently listed exception codes don't exist anymore


 Comments   
Comment by Pierlauro Sciarelli [ 12/Jul/21 ]

alison.huh, you may consider including under this ticket also the v5.0 changes described in the first comment of DOCS-13880 , and leave that ticket as v4.4-only.

Generated at Thu Feb 08 08:10:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.