Document Schemas¶

MongoDB Logo
ServerDriversCloudToolsGuides
Get MongoDB
Close ×
MongoDB Stitch

Introduction
Tutorials
Users & Authentication
MongoDB Atlas
    Overview
    Configure MongoDB
        Link a MongoDB Atlas Cluster
        Define Roles and Permissions
        Filter Incoming Queries
        Enforce a Document Schema
        Configure Advanced Rules
        Specify Cluster Read Preference
        Enable Wire Protocol Connections
    Work With MongoDB
        Add Data to MongoDB
        Find Documents in MongoDB
        Update Documents in MongoDB
        Delete Documents from MongoDB
        Watch for Document Changes
        Run Aggregation Pipelines
        Connect Over the Wire Protocol
    Reference
        MongoDB Actions
        Query Roles
        Query Filters
        Document Schemas
        Connection Strings
        Service Limitations
        CRUD & Aggregation APIs
GraphQL
MongoDB Mobile
Functions
Triggers
External Services
Values & Secrets
Application Deployment
Hosting
Troubleshooting
Stitch Administration
Application Logs
Client SDKs
Release Notes

Stitch > MongoDB Atlas > Reference 

Document Schemas

On this page

Overview
    Schema Enforcement Process
Document Schema Configuration
Schema Data Types
    General
    Objects
    Arrays
    Strings
    Numbers
    Booleans

Overview

A MongoDB service document schema is a JSON object that allows you to define the shape and content of documents and embedded documents in a collection. You can use a schema to require a specific set of fields, configure the content of a field, or to validate changes to a document based on its beginning and ending states.

Document schemas follow the same JSON schema specification as the document validation built in to the MongoDB server. A schema can represent any of the BSON types supported by the $type operator. This page describes schemas for the following common types:

Arrays
Objects
Strings
Numbers
Booleans

Schema Enforcement Process

Stitch evaluates the result of all document writes (inserts and updates) and compares them against the schema before committing the writes to your cluster. If the result of a write operation does not match the schema, Stitch will roll back the write operation and return an error to the user.

Example

A collection has the following document schema:

{
“properties”: {
“_id”: { “bsonType”: “objectId” },
“name”: { “bsonType”: “string” }
}
}

A user with permission to read and write all fields wants to update the name field of a particular document. They issue the following query:

collection.updateOne(
{ “_id”: BSON.ObjectId(“5ae782e48f25b9dc5c51c4d0”) },
{ “$set”: { “name”: 42 } }
)

The query attempts to set the value of name to the number 42, but the schema requires the value to be a string. Stitch will reject this write operation even though the user had permission to update the document because the write result does not conform to the schema.
Document Schema Configuration

Documents in MongoDB are objects stored in a format called BSON, a binary-encoded superset of JSON that supports additional data types. The root of every document schema in Stitch is a BSON Object schema that applies to each document in a collection.

{
“bsonType”: “object”,
“title”: “”,
“required”: ["", …],
“properties”: {
“”:
}
}

Schema Data Types
General

The following fields are available for all schema types:

{
“type”: “” | ["", …],
“bsonType”: “” | ["", …],
“enum”: [<Value 1>, <Value 2>, …],
“description”: ",
“title”: “”
}

Field Name Description
type

The JSON type of the property the schema describes. If the property’s value can be of multiple types, specify an array of JSON types. Cannot be used with the bsonType field.

The following standard JSON types are available:

object
array
number
boolean
string
null

Note

MongoDB’s JSON Schema implementation does not support the integer JSON type. Instead, use the bsonType field with int or long as the value.
bsonType

The BSON type of the property the schema describes. If the property’s value can be of multiple types, specify an array of BSON types. Cannot be used with the type field.

BSON types include all JSON types as well as additional types that you can reference by their string alias, such as:

objectId
int
long
double
decimal
date
timestamp
regex

enum An array that includes all valid values for the data that the schema describes.
title A short title or name for the data that the schema models. This field is used for metadata purposes only and has no impact on schema validation.
description A detailed description of the data that the schema models. This field is used for metadata purposes only and has no impact on schema validation.
Objects

The object schema type configures the content of documents. The following fields are available for object schemas:

For more information, see the official JSON Schema object guide.

{
“bsonType”: “object”,
“title”: “”,
“required”: ["", …],
“properties”: {
“”:
},
“minProperties”: ,
“maxProperties”: ,
“patternProperties”: {
“”:
},
“additionalProperties”: | ,
“dependencies”: {
“”: | ["", …]
}
}

Field Name Description
required An array of field names that must be included in the document.
title A type name for the object. Stitch uses this value to name the document’s type in the GraphQL API.
properties An object where each field maps to a field in the parent object by name. The value of each field is a schema document that configures the value of the field.
minProperties The minimum number of fields allowed in the object.
maxProperties The maximum number of fields allowed in the object.
patternProperties An object where each field is a regular expression string that maps to all fields in the parent object that match. The value of each field is a schema document that configures the value of matched fields.
additionalProperties

Default: true.

If true, a document may contain additional fields that are not defined in the schema. If false, only fields that are explicitly defined in the schema may appear in a document.

If the value is a schema object, any additional fields must validate against the schema.
dependencies Specify property and schema dependencies.
Arrays

The array schema type configures the content of array fields. The following fields are available for array schemas:

For more information, see the official JSON Schema array guide.

{
“bsonType”: “array”,
“items”: | [, …],
“additionalItems”: | ,
“maxItems”: ,
“minItems”: ,
“uniqueItems”:
}

Field Name Description
items A schema for all array items, or an array of schemas where order matters.
additionalItems

Default: true.

If true, the array may contain additional values that are not defined in the schema. If false, only values that are explicitly listed in the items array may appear in the array.

If the value is a schema object, any additional fields must validate against the schema.

Note

The additionalItems field only affects array schemas that have an array-valued items field. If the items field is a single schema object, additionalItems has no effect.
maxItems The maximum length of the array.
minItems The minimum length of the array.
uniqueItems

Default: false

If true, each item in the array must be unique. If false, multiple array items may be identical.
Strings

The string schema type configures the value of string fields. The following fields are available for string schemas:

For more information, see the official JSON Schema string guide.

{
“bsonType”: “string”,
“maxLength”: ,
“minLength”: ,
“pattern”: “”
}

Field Name Description
maxLength The maximum number of characters in the string.
minLength The minimum number of characters in the string.
pattern A regular expression string that must match the string value.
Numbers

The numeric schema type configures the content of numeric fields, such as integers and decimals. The following fields are available for numeric schemas:

For more information, see the official JSON Schema numeric guide.

{
“bsonType”: “int” | “long” | “double” | “decimal”,
“multipleOf”: ,
“maximum”: ,
“exclusiveMaximum”: ,
“minimum”: ,
“exclusiveMinimum”:
}

Field Name Description
multipleOf An integer divisor of the field value. For example, if multipleOf is set to 3, 6 is a valid value but 7 is not.
maximum The maximum value of the number.
exclusiveMaximum

Default: false

If true, the field value must be strictly less than the maximum value. If false, the field value may also be equal to the maximum value.
minimum The minimum value of the number.
exclusiveMinimum

Default: false

If true, the field value must be strictly greater than the minimum value. If false, the field value may also be equal to the minimum value.
Booleans

The boolean schema type configures the content of fields that are either true or false.

For more information, see the official JSON Schema boolean guide.

{ “bsonType”: “bool” }

← Query Filters Connection Strings →

© MongoDB, Inc 2008-present. MongoDB, Mongo, and the leaf logo are registered trademarks of MongoDB, Inc.
Was this page helpful?
Yes
No