[JAVA-5210] Use existing logging component for server detection log message Created: 19/Oct/23 Updated: 10/Jan/24 Resolved: 27/Oct/23 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Logging |
| Affects Version/s: | None |
| Fix Version/s: | 4.11.1 |
| Type: | Improvement | Priority: | Unknown |
| Reporter: | Jeffrey Yemin | Assignee: | Slav Babanin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Documentation Changes: | Not Needed |
| Documentation Changes Summary: | 1. What would you like to communicate to the user about this feature? |
| Description |
|
In scope of https://github.com/mongodb/mongo-java-driver/pull/1214, we added logging for server detection. A new logging component was added with the suffix DefaultClusterFactory. This goes against existing practice of naming loggers based on abstractions that user's understand, rather than internal class names that may change over time. We should use a different logger name for this functionality. I suggest client, as that is one that is already used for a similar purpose (to log MongoClient creation parameters). |
| Comments |
| Comment by Githook User [ 26/Oct/23 ] |
|
Author: {'name': 'Viacheslav Babanin', 'email': 'frest0512@gmail.com', 'username': 'vbabanin'}Message: Update logger name to align with naming conventions. (#1233)
|