[SERVER-42036] Extend JSON Schema implementation to support built-in format formats Created: 02/Jul/19 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 3 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Optimization
|
||||||||
| Participants: | |||||||||
| Description |
|
The JSON Schema specification includes validation of a number of built-in formats: see https://json-schema.org/understanding-json-schema/reference/string.html#built-in-formats. Drafts 6 and 7 of the JSON Schema extend this built-in format validation. The format keyword was never implemented in MongoDB, so we should add it. MongoDB users may wish to validate that their email addresses, ip addresses, hostnames, URIs, and so on are well-formed with an out of the box implementation. |