Azure CosmosDb partition key - different schema

Question

I have an Azure CosmosDB SQP API account with one container "EmployeeContainer", with the partition key "personId". I have three different type of collections in this container. Their schema are as shown below:

Person Collection:

{
    "Id": "1234569",
    "personId" : "P1241234",
    "FirstName": "The first name",
    "LarstName": "The last name"
}

Person-Department Collection:

{
    "Id": "923456757",
    "personId" : "P1241234",
    "departmentId": "dept01",
    "unitId": "unit01",
    "dateOfJoining": "joining date"
}

Department-Employees

{
    "id": "678678",
    "departmentId" : "dept01",
    "departmentName": "IT",
    "employees" : [
        { "personId": "P1241234" },
        { "personId": "P1241235" },
        { "personId": "P1241236" },
    ]   
}

How will the data be stored in the logical partitions? PersonId is the partition key and all the collections have personId in it. So, the document in the person collection with the person id "P1241234" and the document in the Person-Department collection with person id "P1241234" will be stored in the same logical partition? How will be the data in the Department-Employees be stored?

4c74356b41 4c74356b41 · Accepted Answer · 2020-07-06T17:48:35

Yes, that is true, documents with the same personId will be stored under the same logical partition (regardless of their type\schema). I'm not sure you can create documents without the partition key on a collection with a partition key, but if you can - all of them should be under the same logical partition (but I dont think you can create them).

Azure CosmosDb partition key - different schema

2 Answers