EF Core provider gap: No way to know if CreateContainerIfNotExistsAsync actually created the container about azure-cosmos-dotnet-v3

[divega]

It turns out that it is possible to obtain the information of whether the database was created from the status property on the response object, but the API seems to be quite complex.

[j82w]

Hi Deigo,

All of the Async method with throw an exception if it get's an error while creating the container. The exception to this rule is Cosmos Item Stream APIs which only return the status. This is for performance reasons. Also to note that not found is not an exception. This is considered as part of a normal workflow, and will return null for the resource.

The responses are documented here.

[divega]

@j82w the issue was about being able to more easily distinguish between two different conditions when a call to CreateContainerIfNotExistsAsync succeeds:

• The container already exists and didn’t need to be created
• The container did not exist and was successfully created

I will let @AndriySvyryd comment if he still thinks there is an API usability or discoverability problem worth addressing.

[j82w]

@divega if that is the case you can do the read yourself, and if it is null do the create.