No content on Response: Add the ability to have operation return no content from Cosmos DB

[j82w]

Pull Request Template

Description

This adds a flag to get a no content response from Cosmos DB service. This means that create, replace, and upsert operations will have a null response content. This can be lead to a huge improvement in performance by reducing networking traffic and overhead of serializing an object that will never be used.

This is only being exposed on item operations. Two flags are added to make it clear to users that Read can also return with no content. This is great to check if a document exists or not. This also makes it easier in the future to make no content on writes as a default while leaving reads on by default.

public class ItemRequestOptions
{
public virtual bool? NoContentResponseOnWrite {get; set;}
....
}

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Closing issues

closes #1203

[ealsur]

Super cool feature, hoping to see some perf results for Bulk with this on/off

[pentp]

This looks great.
Updated ItemResponse.ETag values are still available as they are part of response headers, right?

[kirankumarkolli]

Will it even makes sense for Feed/Query/Sproc?
If not can it be rooted to ItemReqeustOptions instead?

[j82w]

This looks great.
Updated ItemResponse.ETag values are still available as they are part of response headers, right?

@pentp Yes, etags are still available. I added tests for it.

[jbt00000]

Eureka! It works. Just set the flag and am using it. This is a HUGE perf win. Next up, data compression!?!??!