-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release azure cosmos 3.4.2 #6827
Release azure cosmos 3.4.2 #6827
Conversation
kushagraThapar
commented
Dec 13, 2019
- Changefeed bug fixes (includes all the bug fixes released in 3.3.3)
- Disaster Recovery related bug fixes
- Exception when Cosmos DB HTTP response header is larger than 8192 bytes: [BUG] Exception when Cosmos DB HTTP response header is larger than 8192 bytes #6069
- Vulnerability through dependency in the SDK: [BUG] Vulnerability through dependency in the SDK v3.4.0 #6433
- CosmosSyncScripts null pointer exception in azure-cosmos: [BUG] CosmosSyncScripts null pointer exception in azure-cosmos 3.3.1 #6281
- Default consistency level parsing for Bounded Staleness and Consistent Prefix: ConsistencyPolicy.defaultConsistencyLevel() fails on Bounded Staleness and Consistent Prefix #6707
- Null Value Holder change: Consistency Layer and collection cache optional null value change #6307
Adding changelog and readme updates
/azp run java - cosmos - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
LGTM |
sdk/cosmos/changelog/README.md
Outdated
- Vulnerability through dependency in the SDK: https://github.com/Azure/azure-sdk-for-java/issues/6433 | ||
- CosmosSyncScripts null pointer exception in azure-cosmos: https://github.com/Azure/azure-sdk-for-java/issues/6281 | ||
- Default consistency level parsing for Bounded Staleness and Consistent Prefix: https://github.com/Azure/azure-sdk-for-java/issues/6707 | ||
- Null Value Holder change: https://github.com/Azure/azure-sdk-for-java/issues/6307 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Null Value Holder change is really an internal implementation, we should document it in a way which is more relevant to the end user who reads the changelog. maybe "Cache improvements"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
anyway the changelog can be fixed later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense, will update it in next iteration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done