[SERVER-50435] Restore constness to getInitialDataTimestamp Created: 20/Aug/20  Updated: 29/Oct/23  Resolved: 21/Aug/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 4.4.0
Fix Version/s: 4.7.0

Type: Improvement Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: A. Jesse Jiryu Davis
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

In SERVER-47844 we added the non-const virtual method KVEngine::getInitialDataTimestamp. Strangely, its subclass WiredTigerKVEngine already had a const non-virtual method of the same name. In SERVER-48518 we removed the const non-virtual WiredTigerKVEngine::getInitialDataTimestamp, so it had only its non-const virtual override. Let's clean up after ourselves: getInitialDataTimestamp should be a const virtual method.



 Comments   
Comment by Githook User [ 21/Aug/20 ]

Author:

{'name': 'A. Jesse Jiryu Davis', 'email': 'jesse@mongodb.com', 'username': 'ajdavis'}

Message: SERVER-50435 Restore constness to getInitialDataTimestamp
Branch: master
https://github.com/mongodb/mongo/commit/63e6928e562e90c6d4db60e15279d0b0b7877d67

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