[DOCS-11478] Updated Extended JSON docs to address v2 Created: 21/Mar/18 Updated: 30/Oct/23 Resolved: 12/Aug/19 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Golden | Assignee: | Kay Kim (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: | |||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||
| Days since reply: | 4 years, 26 weeks, 2 days ago | ||||||||||||||||||||||||||||||||
| Epic Link: | DOCSP-1769 | ||||||||||||||||||||||||||||||||
| Story Points: | 2 | ||||||||||||||||||||||||||||||||
| Description |
ScopeThe manual page on Extended JSON needs to be updated to explain the difference between "v1" and "v2" Extended JSON. Some drivers already use v2 and tools will be updated to do so when they are converted to the new in-house Go driver. We need to find a way to let users know about the different forms they might be seeing and about the transition. I'm open to suggestions for the right way to do that. Thanks! drivers that use v2
|
| Comments |
| Comment by Githook User [ 12/Aug/19 ] |
|
Author: {'name': 'Kay Kim', 'username': 'kay-kim', 'email': 'kay.kim@10gen.com'}Message: |
| Comment by Jeffrey Yemin [ 06/May/19 ] |
|
Another bug report ( |
| Comment by David Golden [ 04/Apr/18 ] |
|
That seems like a reasonable approach. That said, "v1" wasn't ever really consistent between server versions, tools versions, drivers, etc. so that probably needs a bit of extra caveat. |
| Comment by Shannon Bradshaw (Inactive) [ 04/Apr/18 ] |
|
david.golden, it seems reasonable to me to have a page for v1 and a separate page for v2. Will the above address the issues you've identified here? |