- Reference >
- Database Commands >
- Administration Commands >
- create
create¶
On this page
Definition¶
-
create¶ Explicitly creates a collection.
createhas the following form:createhas the following fields:Field Type Description createstring The name of the new collection. cappedboolean Optional. To create a capped collection, specify true. If you specifytrue, you must also set a maximum size in thesizefield.autoIndexIdboolean Optional. Specify
falseto disable the automatic creation of an index on the_idfield.Important
For replica sets, all collections must have
autoIndexIdset totrue.sizeinteger Optional. Specify a maximum size in bytes for a capped collection. Once a capped collection reaches its maximum size, MongoDB removes the older documents to make space for the new documents. The sizefield is required for capped collections and ignored for other collections.maxinteger Optional. The maximum number of documents allowed in the capped collection. The sizelimit takes precedence over this limit. If a capped collection reaches thesizelimit before it reaches the maximum number of documents, MongoDB removes old documents. If you prefer to use themaxlimit, ensure that thesizelimit, which is required for a capped collection, is sufficient to contain the maximum number of documents.flagsinteger Optional. Available for the MMAPv1 storage engine only to set the
usePowerOf2Sizesand thenoPaddingflags. To set, specify one of the following values:0corresponds tousePowerOf2Sizesflag set tofalseandnoPaddingflag set tofalse.1corresponds tousePowerOf2Sizesflag set totrueandnoPaddingflag set tofalse.2corresponds tousePowerOf2Sizesflag set tofalseandnoPaddingflag set totrue.3corresponds tousePowerOf2Sizesflag set totrueandnoPaddingflag set totrue.
Note
MongoDB 3.0 ignores the
usePowerOf2Sizesflag. SeecollModanddb.createCollection()for more information.Defaults to
1.New in version 2.6.
Changed in version 3.0.0: Add support for setting the new
noPaddingflag.Warning
Do not set
noPaddingif the workload includes removes or any updates that may cause documents to grow. For more information, see No Padding Allocation Strategy.storageEnginedocument Optional. Available for the WiredTiger storage engine only.
New in version 3.0.
Allows users to specify configuration to the storage engine on a per-collection basis when creating a collection. The value of the
storageEngineoption should take the following form:Storage engine configuration specified when creating collections are validated and logged to the oplog during replication to support replica sets with members that use different storage engines.
The
db.createCollection()method wraps thecreatecommand.
Considerations¶
The create command obtains a write lock on the
affected database and will block other operations until it has
completed. The write lock for this operation is typically short
lived. However, allocations for large capped collections may take
longer.
Examples¶
Create a Capped Collection¶
To create a capped collection limited to 64 kilobytes, issue the command in the following form:
Specify Storage Engine Options¶
New in version 3.0.
You can specify collection-specific storage engine configuration
options when you create a collection with
db.createCollection(). Consider the following operation:
This operation creates a new collection named users with a
specific configuration string that MongoDB will pass to the
wiredTiger storage engine. See the WiredTiger documentation of
collection level options
for specific wiredTiger options.