|
3 | 3 | The purpose of this guide is to detail changes made by successive |
4 | 4 | versions of the Java driver. |
5 | 5 |
|
| 6 | +### 2.1.8 |
| 7 | + |
| 8 | +2.1.8 is binary-compatible with 2.1.7 but introduces a small change in the |
| 9 | +driver's behavior: |
| 10 | + |
| 11 | +1. The list of contact points provided at startup is now shuffled before trying |
| 12 | + to open the control connection, so that multiple clients with the same contact |
| 13 | + points don't all pick the same control host. As a result, you can't assume that |
| 14 | + the driver will try contact points in a deterministic order. In particular, if |
| 15 | + you use the `DCAwareRoundRobinPolicy` without specifying a primary datacenter |
| 16 | + name, make sure that you only provide local hosts as contact points. |
| 17 | + |
| 18 | + |
6 | 19 | ### 2.1.7 |
7 | 20 |
|
8 | 21 | This version brings a few changes in the driver's behavior; none of them break |
@@ -41,14 +54,6 @@ binary compatibility. |
41 | 54 | If you know that the CQL functions or expressions are safe, use |
42 | 55 | `setIdempotent(true)` on the statement. |
43 | 56 |
|
44 | | -5. The list of contact points provided at startup is now shuffled before trying |
45 | | - to open the control connection, so that multiple clients with the same contact |
46 | | - points don't all pick the same control host. As a result, you can't assume that |
47 | | - the driver will try contact points in a deterministic order. In particular, if |
48 | | - you use the `DCAwareRoundRobinPolicy` without specifying a primary datacenter |
49 | | - name, make sure that you only provide local hosts as contact points. |
50 | | - |
51 | | - |
52 | 57 | ### 2.1.6 |
53 | 58 |
|
54 | 59 | See [2.0.10](#2-0-x-to-2-0-10). |
|
0 commit comments