[SERVER-59802] discrepancy in audit log output - for findAndModify command Created: 05/Sep/21 Updated: 07/Sep/21 Resolved: 07/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.4.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Dror Mikdash (Inactive) | Assignee: | Eric Sedor |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Case: | (copied to CRM) | ||||
| Description |
|
The capitalization in the audit.log logline is findandmodify (in the “args_” array )when findAndModify is launched from the same machine as mongod |
| Comments |
| Comment by Eric Sedor [ 07/Sep/21 ] |
|
Initially it looks like this difference is introduced on the client side through support for different cased versions of the findAndModify command |