[SERVER-47697] Make logger:: typedefs to logv2::LogSeverity, logv2::LogComponent, etc Created: 22/Apr/20  Updated: 29/Oct/23  Resolved: 24/Apr/20

Status: Closed
Project: Core Server
Component/s: Logging
Affects Version/s: None
Fix Version/s: 4.4.1, 4.7.0

Type: Improvement Priority: Major - P3
Reporter: Billy Donahue Assignee: Billy Donahue
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Issue split
split from SERVER-47207 upgrade setParameter & getParameter t... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4
Sprint: Service arch 2020-05-04
Participants:

 Description   

The logger and logv2 namespaces have separate but identical implementations of LogSeverity, LogComponent, and LogComponentSettings. This causes pain in logv2 upgrades because we have to cast back and forth and it's unclear whether the namespaces are significant (they aren't).

Move the tests for these types into the logv2/ directory. After doing so, there are no more relevant logger/log_test.cpp tests, so a number of logger files can be eliminated and we won't have to maintain them anymore.



 Comments   
Comment by Githook User [ 02/May/20 ]

Author:

{'name': 'Billy Donahue', 'email': 'billy.donahue@mongodb.com', 'username': 'BillyDonahue'}

Message: SERVER-47697 Remove logging/log_test.cc and support files.

  • LogComponent aliased
  • LogSeverity aliased
  • LogComponentSettings testing
  • all relevant tests moved to logv2.
  • bye bye log_test.cpp!

(cherry picked from commit 7b1053b738c3c6b0c634e39bf8f70a66fffc1ee0)
Branch: v4.4
https://github.com/mongodb/mongo/commit/9cf5e9a0ecd0f0472705cc3477d3abfa7f3f35b7

Comment by Githook User [ 23/Apr/20 ]

Author:

{'name': 'Billy Donahue', 'email': 'billy.donahue@mongodb.com', 'username': 'BillyDonahue'}

Message: SERVER-47697 Remove logging/log_test.cc and support files.

Comment by Billy Donahue [ 22/Apr/20 ]

CR http://mongodbcr.appspot.com/571230002

Generated at Thu Feb 08 05:14:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.