When I run the tool graphically (dtui.exe) and specify a source of JSON files and a destination of CosmosDB, and the collection I choose to import to doesn't exist, the tool automatically creates it before importing items.
However I would like the collection to respect shared throughput on the database it belongs to i.e. equivalent to having the "Provision dedicated throughput" option unchecked were I to create the collection in the portal. There doesn't seem to be any way to do this. The relevant code seems to be DocumentDbClient which always expects a parameter desiredThroughput and always supplies a RequestOptions with OfferThroughput set. I would expect that this would be the setting that configures a new collection with dedicated throughput, whereas not specifying it would honour shared throughput.
When I run the tool graphically (dtui.exe) and specify a source of JSON files and a destination of CosmosDB, and the collection I choose to import to doesn't exist, the tool automatically creates it before importing items.
However I would like the collection to respect shared throughput on the database it belongs to i.e. equivalent to having the "Provision dedicated throughput" option unchecked were I to create the collection in the portal. There doesn't seem to be any way to do this. The relevant code seems to be DocumentDbClient which always expects a parameter
desiredThroughputand always supplies aRequestOptionswithOfferThroughputset. I would expect that this would be the setting that configures a new collection with dedicated throughput, whereas not specifying it would honour shared throughput.