[DOCS-14176] Add options for new Server Discovery and Monitoring engine to example for version 3.6 of the Node driver Created: 02/Feb/21 Updated: 29/Oct/23 Resolved: 08/Mar/21 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | drivers |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Brian Leonard | Assignee: | Nathan Leniz |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 2 years, 48 weeks, 5 days ago | ||||
| Epic Link: | DOCSP-9026 | ||||
| Story Points: | 2 | ||||
| Description |
DescriptionFollowing the Node.js Connection Guide will return a Deprecation Warning: (node:98468) DeprecationWarning: current Server Discovery and Monitoring engine is deprecated, and will be removed in a future version. To use the new Server Discover and Monitoring engine, pass option { useUnifiedTopology: true } to the MongoClient constructor. Passing the following to the MongoClient resolves the warning: ,{ useNewUrlParser: true, useUnifiedTopology: true }
Scope of changesCut a 3.6 branch and change the connection guide and all examples to include connection options that became default in 4.0 Impact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Nathan Leniz [ 06/Mar/21 ] |