[SERVER-8552] setParameter command has confusing behavior when setting multiple parameters. Created: 13/Feb/13 Updated: 10/May/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 2.4.0-rc0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | DO NOT USE - Backlog - Platform Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | move-sa, platforms-re-triaged, triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
The result of a successful setParameter with one parameter to set is { was: <old value>, ok: 1 }. However, if you set two parameters, you get back { was: <first old value>, was: <second old value>, ok: 1}, which many client drivers seem to turn into { was: <one of the old values>, ok: 1}. Further, if you pass multiple parameters to setParameter, and one of the sets fails, some of the parameters will have been set and some not, and the response will contain a "was" field for one of the successful sets, ok: 0 and errmsg of "not allowed to change [<first encountered unsettable field>]" or some such. |
| Comments |
| Comment by Steven Vannelli [ 10/May/22 ] |
|
Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions. |