[DOCS-12215] resetError deprecation status Created: 20/Nov/18  Updated: 30/Oct/23  Resolved: 13/Dec/19

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Trivial - P5
Reporter: Oleg Pudeyev (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-33226 Get rid of the `getPrevError` command Closed
Related
Participants:
Days since reply: 4 years, 8 weeks, 5 days ago
Epic Link: DOCSP-1769

 Description   

Description

This page: https://docs.mongodb.com/manual/reference/command/resetError/ does not mention that resetError is deprecated. https://docs.mongodb.com/manual/reference/method/db.resetError/#db.resetError says the db command is deprecated since 1.6.

For comparison, https://docs.mongodb.com/manual/reference/command/getPrevError/ says it's deprecated since 3.6 and https://docs.mongodb.com/manual/reference/method/db.getPrevError/#db.getPrevError says it's deprecated since 1.6.

Scope of changes

Investigating whether resetError is actually deprecated in the same way as getPrevError. If so, mark what version to consider resetError as deprecated. 

 

  status
​ db.getPrevError
  • deprecated in 1.6 DOCS-142 with githubcommit
  • removed in 4.2 – SERVER-33226 (need to mark as docs needed  so that corresponding docs ticket generated ugh, because the  downstream flag is different from before with separate docs changes needed, will just manually link this ticket as Documents that ticket. ) ​
getPrevError command
db.resetError
resetError command Will mark as deprecated without specifying since when.   

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Kay Kim (Inactive) [ 13/Dec/19 ]

++Will publish changes on Monday

Comment by Githook User [ 13/Dec/19 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-12215: 4.2 remove deprecated getPrevError
Branch: master
https://github.com/mongodb/docs/commit/618f8fc2eea7e152d18a2901ba9cf216e2ef3de3

Comment by Githook User [ 13/Dec/19 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-12215: annotate reset/getprevError as deprecated
Branch: master
https://github.com/mongodb/docs/commit/ab567ef2dcb00e9400ad9188e133b5c914ae638a

Comment by Githook User [ 13/Dec/19 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-12215: annotate reset/getprevError as deprecated
Branch: v3.6
https://github.com/mongodb/docs/commit/6c1046304fcc8e8ce4210caf05f537876523998e

Comment by Githook User [ 13/Dec/19 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-12215: annotate reset/getprevError as deprecated
Branch: v4.0
https://github.com/mongodb/docs/commit/c6a25de85c6a3155a0c534a18a1c819ccb3069c8

Comment by Ravind Kumar (Inactive) [ 26/Nov/18 ]

I can mark the commands and their shell helpers as 'deprecated and will be removed in a future version'. If I remember I'll open a SERVER ticket to call out resetError and link it to SERVER-33226

Thanks all. 

Comment by Asya Kamsky [ 26/Nov/18 ]

Yes, since the command has no purpose without getLastError/getPrevError it should be deprecated/removed along with them.

Comment by Kaloian Manassiev [ 26/Nov/18 ]

CC asya to answer this question.

Comment by Ravind Kumar (Inactive) [ 20/Nov/18 ]

Is resetError actually deprecated? I don't see it commented with any deprecation warnings in code. For getPrevError, discussions around SERVER-33226 indicated that the command would be removed wholesale, but there were no references to resetError. I don't actually see where the work itself was done anywhere, it kind of seems like we marked the command as deprecated in docs but have no other indicators/markers that this command should go poof at some point.

kaloian.manassiev can you shed some light on this? SERVER-29908 is the last time I see that the cluster_get_prev_error.ccp file was touched. I don't see any other SERVER or DOCS tickets in fact with regards to whether resetError or getPrevError are actually toast in 4.0. 

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