Summarize IDL changes re Compatibility Notes API V1
(DOCS-14385)
|
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Sub-task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Joseph Dougherty |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 2 years, 41 weeks, 1 day ago | ||||||||
| Description |
DescriptionDownstream Change Summary The createIndexes command had permitted values of the wrong type for at least some of the following options: background, unique, sparse, finestIndexedLevel, coarsestIndexedLevel, dropDups, weights, default_language, language_override, wildcardProjection, 2dsphereIndexVersion, textIndexVersion, bits, min, and max. In All valid invocations of createIndexes should work the same as before, but misformatted invocations that had silently misbehaved heretofore will be rejected henceforth. Description of Linked Ticket My change to the "listIndexes" IDL (
(In retrospect, we should've converted createIndexes before listIndexes, but I didn't anticipate this issue.) I made createIndexes validate the "background" option in this commit, now I'll validate the rest of the options. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Joseph Dougherty [ 27/Apr/21 ] |
|
The createIndexes command is documented on the 5.0 Compatibility Changes page: Command behavior re rejecting invalid arguments is documented on the Versioned API page: |