Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Done
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Server Programmability
Backwards Compatibility:
Fully Compatible
Sprint:
Programmability 2025-03-31, Programmability 2025-04-14, Programmability 2025-04-28, Programmability 2025-05-12
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

We have multiple JSON parsers in our system. Worse, some of them are near-JSON, with different parsing behavior.

Ideally we'd use third-party JSON parsers, or at least have one JSON parser for all use cases. This ticket should determine how close we can get, and file work items to get us there.

is related to

SERVER-104025 Consolidate our uses of alternate JSON-to-BSON parsers onto the standard one

Blocked

related to

SERVER-104553 Use standard JSON to express JSON string literals

Backlog

SERVER-104573 Reimplement fromFuzzerJson() using a third-party JSON parser

Backlog

SERVER-102006 Discover all parsers in our system and determine current level of testing.

Closed

SERVER-104547 Reject invalid JSON arguments to server parameters and commandline parameters

Needs Scheduling

WT-14460 Ensure WT errors are expressed to server code in standard JSON

Needs Scheduling

(1 related to)

Assignee:: James Bronsted
Reporter:: Ronald Steinke
Participants:: James Bronsted, Ronald Steinke
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Due:: 18/Apr/25
Created:: Mar 10 2025 02:21:24 PM UTC
Updated:: May 01 2025 03:28:03 PM UTC
Resolved:: May 01 2025 03:28:02 PM UTC
Confidence Status Last Update:: 18/Mar/25 7:31 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates