Skip to content

Commit 14dccbb

Browse files
committed
Fixing create collection for MongoDB
1 parent e6f128c commit 14dccbb

File tree

3 files changed

+32
-1
lines changed

3 files changed

+32
-1
lines changed

articles/cosmos-db/create-mongodb-java.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ In this quickstart, you create and manage an Azure Cosmos DB for MongoDB API acc
3838

3939
Name your new database **db**, and your new collection **coll**.
4040

41-
[!INCLUDE [cosmos-db-create-collection](../../includes/cosmos-db-create-collection.md)]
41+
[!INCLUDE [cosmos-db-create-collection](../../includes/cosmos-db-mongodb-create-collection.md)]
4242

4343
## Clone the sample application
4444

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
title: include file
3+
description: include file
4+
services: cosmos-db
5+
author: LuisBosquez
6+
ms.service: cosmos-db
7+
ms.topic: include
8+
ms.date: 04/08/2020
9+
ms.author: lbosq
10+
ms.custom: include file
11+
---
12+
13+
You can now use the Data Explorer tool in the Azure portal to create an Azure Cosmos DB's API for MongoDB database and container.
14+
15+
1. Select **Data Explorer** > **New Container**.
16+
17+
The **Add Container** area is displayed on the far right, you may need to scroll right to see it.
18+
19+
![The Azure portal Data Explorer, Add Container pane](./media/cosmos-db-create-collection/azure-cosmosdb-mongodb-data-explorer.png)
20+
21+
2. In the **Add container** page, enter the settings for the new container.
22+
23+
|Setting|Suggested value|Description
24+
|---|---|---|
25+
|**Database ID**|db|Enter *db* as the name for the new database. Database names must contain from 1 through 255 characters, and they cannot contain `/, \\, #, ?`, or a trailing space. Check the **Provision database throughput** option, it allows you to share the throughput provisioned to the database across all the containers within the database. This option also helps with cost savings. |
26+
|**Throughput**|400|Leave the throughput at 400 request units per second (RU/s). If you want to reduce latency, you can scale up the throughput later. You can also choose [Autopilot mode](https://docs.microsoft.com/azure/cosmos-db/provision-throughput-autopilot), which will give you a range of RU/s that will dynamically increase and decrease as needed.|
27+
|**Collection ID**|coll|Enter *coll* as the name for your new container. Container IDs have the same character requirements as database names.|
28+
|**Storage capacity**|Fixed (10GB)|Enter *Fixed (10GB)* for this application. If you select *Unlimited*, you will have to create a `Shard Key`, which all items inserted will require.|
29+
|**Shard key**| /_id| The sample described in this article does not use a Shard Key, so setting it to */_id* will use the automatically generated ID field as the shard key. Learn more about sharding, also known as partitioning, in [Partitioning in Azure Cosmos DB](https://docs.microsoft.com/azure/cosmos-db/partitioning-overview)|
30+
31+
Select **OK**. The Data Explorer displays the new database and container.
41.5 KB
Loading

0 commit comments

Comments
 (0)