We're having some trouble and tons of confusion about choosing the correct version of BulkExecutor with .Net cosmos SDK, currently we're building 2 class library projects using different versions of cosmos DB SDK
The first class library project we're using .Net Core with Microsoft.Azure.Cosmos 3.0.0 (v3) package, we use this for reading an item from Cosmos DB collection.
The second class library project we've tried with .Net Framework 4.6.1/4.7.1 with Microsoft.Azure.Documents.Client which is the v2 package, we use this for bulkInsert or bulkUpdate item collections with Cosmos DB, yes the bulkexecutor was used here.
However, when our v3 project add the reference of v2 project, we're not able to initialize
v2 connection of cosmos db using Microsoft.Azure.Documents.Client, I wonder if it's an issue
of different versions of Cosmos DB SDK being used here? Could we use the combination of v2 and v3 in same solution? Is it possible to use the bulk executor with v3 of Cosmos .NET SDK?
We're having some trouble and tons of confusion about choosing the correct version of BulkExecutor with .Net cosmos SDK, currently we're building 2 class library projects using different versions of cosmos DB SDK
The first class library project we're using .Net Core with Microsoft.Azure.Cosmos 3.0.0 (v3) package, we use this for reading an item from Cosmos DB collection. The second class library project we've tried with .Net Framework 4.6.1/4.7.1 with Microsoft.Azure.Documents.Client which is the v2 package, we use this for bulkInsert or bulkUpdate item collections with Cosmos DB, yes the bulkexecutor was used here.
However, when our v3 project add the reference of v2 project, we're not able to initialize v2 connection of cosmos db using Microsoft.Azure.Documents.Client, I wonder if it's an issue of different versions of Cosmos DB SDK being used here? Could we use the combination of v2 and v3 in same solution? Is it possible to use the bulk executor with v3 of Cosmos .NET SDK?