- Test that $jsonSchema is illegal in arrayFilters.
- Test that $jsonSchema is illegal in partial filter expressions.
- Test that $jsonSchema is legal in read commands like count, geoNear, and distinct.
- Test that $jsonSchema is legal in predicates for write commands (delete, update, and findAndModify). We should also ensure that such writes can replicate correctly.
- Test $jsonSchema in the precondition checking for applyOps?
- Test that $jsonSchema does not respect either the collection-default collation or a collation set explicitly on a query.
- Test that $jsonSchema can be included in a $match stage within a view. This should include a multiversion test which ensures that once this view has been created, you cannot downgrade to 3.4. We might also want to write a descriptive check showing that view creation with $jsonSchema is not gated on feature compatibility version.
- Test $jsonSchema queries alongside $text and $geoNear
- Test $jsonSchema in a sharded cluster where the schema contains the shard key.
- Test $jsonSchema within an eval command.
- Test index usage for queries containing $jsonSchema
- Test $jsonSchema in an $elemMatch projection
- Test queries containing $jsonSchema wrapped in logical operator(s) ($or, $and,...)
- depends on
-
SERVER-30987 Enable and test $jsonSchema in the aggregation $match stage
- Closed
- related to
-
SERVER-31201 JSON Schema inside an arrayFilter should be disallowed
- Closed