Skip to content

Updated changelog and readme #6123

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.

Sign up for GitHub

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

Merged
kushagraThapar merged 2 commits into from
Nov 1, 2019
Merged

Updated changelog and readme #6123

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
49f3af6
Updated changelog and readme
kushagraThapar Oct 31, 2019
f62f9dc
Minor update
kushagraThapar Nov 1, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 6 additions & 7 deletions sdk/cosmos/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,9 +89,9 @@ For example, using maven, you can add the following dependency to your maven pom

```xml
<dependency>
<groupId>com.microsoft.azure</groupId>
<groupId>com.azure</groupId>
<artifactId>azure-cosmos</artifactId>
<version>3.1.0</version>
<version>4.0.0-preview.1</version>
</dependency>
```

Expand Down Expand Up @@ -151,16 +151,15 @@ readItemMono
After result is received if you want to do CPU intensive work on the result you should avoid doing so on eventloop IO netty thread. You can instead provide your own Scheduler to provide your own thread for running your work.

```java
import rx.schedulers;

Mono<CosmosItemResponse> readItemMono = item.read();

readItemMono
.subscribeOn(Schedulers.computation())
.subscribeOn(Schedulers.parallel())
.subscribe(
resourceResponse -> {
// this is executed on threads provided by Scheduler.computation()
// Schedulers.computation() should be used only the work is cpu intensive and you are not doing blocking IO, thread sleep, etc. in this thread against other resources.
// this is executed on threads provided by Scheduler.parallel()
// Schedulers.parallel() should be used only when the work is cpu intensive and you are not doing blocking IO, thread sleep, etc. in this thread against other resources.
veryCpuIntensiveWork();
});

Expand Down Expand Up @@ -218,7 +217,7 @@ and add the following dependency to your project maven dependencies:
<dependency>
<groupId>io.netty</groupId>
<artifactId>netty-tcnative</artifactId>
<version>2.0.25.Final</version>
<version>2.0.26.Final</version>
<classifier>linux-x86_64</classifier>
</dependency>
```
Expand Down
19 changes: 19 additions & 0 deletions sdk/cosmos/changelog/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,24 @@
## Changelog

### 4.0.0-preview.1
- GroupId change from com.microsoft.azure to com.azure
- Namespace changes from microsoft-azure-cosmos to azure-cosmos
- Getter and Setter changes to get() & set() pattern

### 3.3.1
- Added @JsonIgnore on getLogger in JsonSerializable

### 3.3.0
- **Version Upgrades**
- Project Reactor version upgrade to 3.3.0.RELEASE
- reactor-netty version upgrade to 0.9.0.RELEASE
- netty version upgrade to 4.1.42.Final
- netty-tcnative version upgrade to 2.0.26.Final
- **Bug Fixes**
- Retry not happening on direct mode for Request Rate Too Large Exception
- NPE on Not Found, Gone, PartitionSplit Exception.
- Change Feed Processor: fix a handful of bugs related to not-reactor/blocking calls, preserving the current continuation token in the lease documents and proper load balancing of the current workload when more than one host is running at a given time.

### 3.1.0
- Added CosmosKeyCredential support in CosmosClientBuilder to support account key rotation.

Expand Down