[SERVER-29584] Create a $schemaRequiredProperties MatchExpression Created: 12/Jun/17  Updated: 06/Dec/22  Resolved: 07/Jul/17

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Kyle Suarez Assignee: Backlog - Query Team (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query
Sprint: Query 2017-07-31
Participants:

 Comments   
Comment by David Storch [ 07/Jul/17 ]

kyle.suarez, nah, we've kept other such tickets in the Epic so it seems fine to leave in.

Comment by Kyle Suarez [ 07/Jul/17 ]

david.storch, closed as Won't Fix for the reasons stated above.

Does it also get kicked out of the epic?

Comment by David Storch [ 07/Jul/17 ]

kyle.suarez, good point, I don't think we actually need this. We probably shouldn't build this for convenience, but rather should just take advantage of existing MatchExpression features. For example, consider the following translation. As JSON Schema:

{$jsonSchema: {
    type: "object",
    properties: {
        a: {type: "string"},
        b: {type: "number"},
    },
    required: ["a"]
}

As a MatchExpression:

{a: {$type: "string"}, $or: [{b: {$exists: false}}, {b: {$type: "number"}}]}

Recommend closing this ticket as Won't Fix.

Comment by Kyle Suarez [ 06/Jul/17 ]

Thinking about this more, it might suffice to simply use $exists. But I do think there is a slight element of convenience in having this.

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