Skip to content

Conversation

@jeet1995
Copy link
Member

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

All SDK Contribution checklist:

  • The pull request does not introduce [breaking changes]
  • CHANGELOG is updated for new features, bug fixes or other significant changes.
  • I have read the contribution guidelines.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

* Add a way to tune max item count for change feed requests when `StreamsConstrainedException` is hit.

* Add a way to tune max item count for change feed requests when `StreamConstraintsException` is hit.

* Add a way to tune page size / skip "un"-parseable document.

* Add a way to tune page size / skip "un"-parseable document.

* Addressing review comments.

* Addressing review comments.

* Addressing review comments.

* Wire eTag to CosmosException.

* Enhance tests.

* Addressing logging.

* Addressing logging.

* Addressing NPEs.

* Addressing continuation issues.

* Fixing compilation errors.

* Addressing review comments.

* Addressing review comments.

* Addressing review comments.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant