Skip to content

Added content response on write enabled feature to Gateway and Direct TCP#10741

Merged
kushagraThapar merged 7 commits intoAzure:masterfrom
kushagraThapar:cosmos_return_minimal_response_feature
May 7, 2020
Merged

Added content response on write enabled feature to Gateway and Direct TCP#10741
kushagraThapar merged 7 commits intoAzure:masterfrom
kushagraThapar:cosmos_return_minimal_response_feature

Conversation

@kushagraThapar
Copy link
Member

@kushagraThapar kushagraThapar commented May 6, 2020

This PR:

  • Adds contentResponseOnWriteEnabled argument to CosmosClientBuilder and all internal client builders.
  • By default the value for the argument is set to false -> Item write operations will not return content response.
  • This feature only works in Gateway and Direct TCP mode. (Direct HTTP is implemented on the backend, but needs to be released)
  • Exposes new APIs - getETag() on CosmosItemResponse and CosmosAsyncItemResponse
  • Added configuration options for Write Throughput and Write Latency Benchmarks.
  • Updated client builders in TestSuiteBase to support contentResponseOnWriteEnabled testing.
  • Updated and closed some open github issues that have already been fixed.

Copy link
Member

@kirankumarkolli kirankumarkolli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Waiting on name closure

Updated cosmos container and database tests to emulator groups.
Removed prefer header generic logic
@kushagraThapar kushagraThapar changed the title Added return minimal response feature to Gateway and Direct TCP Added no content response on write feature to Gateway and Direct TCP May 6, 2020
@kushagraThapar
Copy link
Member Author

/azp run java - cosmos - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kirankumarkolli
Copy link
Member

Would be nice to behcnmark with this change in.

Copy link
Contributor

@moderakh moderakh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

some minor comments. other than that LGTM

Copy link

@David-Noble-at-work David-Noble-at-work left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kushagraThapar kushagraThapar changed the title Added no content response on write feature to Gateway and Direct TCP Added content response on write enabled feature to Gateway and Direct TCP May 6, 2020
@kushagraThapar
Copy link
Member Author

/azp run java - cosmos - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

… clients with content response on write flag
@kushagraThapar
Copy link
Member Author

/azp run java - cosmos - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kushagraThapar
Copy link
Member Author

/azp run java - cosmos - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kushagraThapar
Copy link
Member Author

/azp run java - cosmos - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kushagraThapar
Copy link
Member Author

/azp run java - cosmos - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kushagraThapar
Copy link
Member Author

kushagraThapar commented May 7, 2020

Single region session long CI failed after running all the tests successfully with spot bugs jar downloads.

2020-05-07T15:44:56.2558748Z [ERROR] Failed to execute goal com.github.spotbugs:spotbugs-maven-plugin:3.1.12.2:spotbugs (spotbugs) on project azure-cosmos: Execution spotbugs of goal com.github.spotbugs:spotbugs-maven-plugin:3.1.12.2:spotbugs failed: Plugin com.github.spotbugs:spotbugs-maven-plugin:3.1.12.2 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.bcel:bcel:jar:6.3.1, net.jcip:jcip-annotations:jar:1.0, org.dom4j:dom4j:jar:2.1.1, jaxen:jaxen:jar:1.1.6: Could not transfer artifact org.apache.bcel:bcel:jar:6.3.1 from/to ossrh (https://oss.sonatype.org/content/repositories/snapshots/): Transfer failed for https://oss.sonatype.org/content/repositories/snapshots/org/apache/bcel/bcel/6.3.1/bcel-6.3.1.jar: Connection reset -> [Help 1]

@kushagraThapar
Copy link
Member Author

Single Region Strong Https e2e failed because of lots of SSLEngine closed already reactor-netty issue.
I think it might have caused the VM to crash. I have added more information on this issue:
#7349

@kushagraThapar kushagraThapar merged commit 3742ebf into Azure:master May 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

Comments