[SERVER-62648] Eliminate std::cerr from new optimizer logging Created: 14/Jan/22  Updated: 29/Oct/23  Resolved: 28/Jun/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Improvement Priority: Minor - P4
Reporter: Svilen Mihaylov (Inactive) Assignee: Matt Boros
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: QO 2022-02-07, QO 2022-02-21, QO 2022-03-07, QO 2022-03-21, QO 2022-04-04, QO 2022-04-18, QO 2022-05-02, QO 2022-05-16, QO 2022-05-30, QO 2022-06-13, QO 2022-06-27, QO 2022-07-11
Participants:

 Description   

Currently we use it to ease debugging. Consider updating to use structured logging or other means.



 Comments   
Comment by Githook User [ 27/Jun/22 ]

Author:

{'name': 'Matt Boros', 'email': 'matt.boros@mongodb.com', 'username': 'mattBoros'}

Message: SERVER-62648 Eliminate std::cerr from new optimizer logging
Branch: master
https://github.com/mongodb/mongo/commit/4026c62f484991122e39c8234382c33c5b30ad5e

Comment by Kyle Suarez [ 14/Jan/22 ]

Query Execution thinks this is important to schedule soon (right after the optimizer-poc merge?), but it feels more appropriate on the Optimization team, so punting this ticket across.

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