[DOCS-12150] 3.4 Compatibility Notes has an example of a command that doesn't work, but it does Created: 18/Oct/18 Updated: 30/Oct/23 Resolved: 18/Oct/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Joanna Cheng | Assignee: | Kay Kim (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 5 years, 17 weeks ago | ||||||||
| Epic Link: | DOCSP-1769 | ||||||||
| Description |
Descriptionhttps://docs.mongodb.com/manual/release-notes/3.4-compatibility/#stricter-validation-of-collection-and-index-specifications says
However, this command works fine on my 3.4.16 node
It also matches the spec in the same docs https://docs.mongodb.com/manual/reference/method/db.createCollection/#db.createCollection Can we change this example in the docs? It's not clear if there's something specific we want to demonstrate, but you have to specify valid options, so this no longer works:
Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Kay Kim (Inactive) [ 18/Oct/18 ] |
|
Will publish tomorrow morning. |
| Comment by Githook User [ 18/Oct/18 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 18/Oct/18 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 18/Oct/18 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 18/Oct/18 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |