[SERVER-36778] Make 3.2 client metadata log messages match 3.4+ format Created: 21/Aug/18 Updated: 29/Oct/23 Resolved: 22/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | 3.2.20 |
| Fix Version/s: | 3.2.21 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Kevin Pulo |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Minor Change | ||||||||
| Participants: | |||||||||
| Description |
|
It will help with processing if the messages output by 3.2 when client metadata is received in the isMaster command (added in There is still no full support for client metadata in MongoDB 3.2, merely these log messages when the info is received, as a way of ensuring that 3.4+ compatible drivers are in use prior to upgrading the server from 3.2 to 3.4. |
| Comments |
| Comment by Githook User [ 22/Aug/18 ] |
|
Author: {'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com', 'username': 'devkev'}Message: |