Cosmos Bulk Delete Response Status {statusCode: -1, requestCharge: 0}

[sergsalo]

@azure/cosmos
3.9.3
NodeJS 12

When Bulk operation is executed next response is returned:

{statusCode: -1, requestCharge: 0}

Expected behavior
successful status code with a body of deleted item

Additional context

My CosmosDB instance doesn't have partitionKey, so I don't pass it.

 await container.items.bulk([{  
        id: docId,
        operationType: "Delete",
}]);

docId sample: 'ad159f73-9368-451a-8765-48ebd7772a1e'

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @southpolesteve, @zfoster

[sergsalo]

const write = await container.items.bulk([
      {
        resourceBody: {
          id: "foo ad159f73-9368-451a-8765-48ebd7772a1e",
          name: "foo",
        },
        operationType: "Upsert",
      },
    ]);
    const read = await container.items.bulk([
      {
        id: "foo ad159f73-9368-451a-8765-48ebd7772a1e",
        operationType: "Read",
      },
    ]);
    const bulkDelete = await container.items.bulk([
      {
        id: "foo ad159f73-9368-451a-8765-48ebd7772a1e",
        operationType: "Delete",
      },
    ]);

write - works
read and delete - return statusCode = -1

[southpolesteve]

Thanks for the detailed repo @sergsalo. We will investigate.

[zfoster]

We may have a bug in the type here @sergsalo. The read and delete operations should work if you pass partitionKey: {} as an argument. Read/Delete require a partitionKey since we can't extract one without a body present in the args

[zfoster]

Actually, I just wrote a patch that will default the partitionKey for Read/Delete operations if it's not present

[sergsalo]

great, do you know when this will be released?

[zfoster]

@sergsalo within a couple days. For sure by end of the week Friday