Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-51013

Improve granularity of $jsonSchema validation errors in the case of inversion

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Query Execution

    Description

      Currently, any $jsonSchema validator expression which features a negation will simply state that the child expression or the schema matched (ex. given expression {$nor: [{$jsonSchema: {}}]} or {$jsonSchema: {not: {}}} and the document {}, you will get "schema matched" in the first case and "child expression matched" the second case). This ticket tracks the work necessary to make inversion provide detailed errors.

      Note that this has a surprising amount of complexity, namely because of the semantics of various $jsonSchema keywords and the way that some keywords are translated into MatchExpression.

      Attachments

        Activity

          People

            backlog-query-execution Backlog - Query Execution
            mihai.andrei@mongodb.com Mihai Andrei
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: