[SERVER-12883] getLastErrorModes should be renamed Created: 25/Feb/14  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Replication
Affects Version/s: 2.6.0-rc0
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Osmar Olivo Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
Assigned Teams:
Replication
Participants:

 Description   

Given that all writes will use the new write API as of 2.6, getLastErrorModes for custom write concerns/tagging write concerns is somewhat of a name rooted in legacy and is no longer a good fit.

If I want to use a custom write concern, it is very unintuitive for me to know that getLastErrorModes is the configuration flag to do so. Especially considering that getLastError() is no longer how write concerns internally work.


Generated at Thu Feb 08 03:29:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.