DSE 6.8.49 Release Notes #145
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| * Upgraded JDK 8 and 11 versions in DSE Docker images to `8u402` and `11.0.22` respectively. (DSP-24250) | ||
|
|
||
| ## 6.8.49 DSE Driver | ||
| * Upgrades `dse-java-driver` to handle newer versions of Guava. (DSP-24191) |
There was a problem hiding this comment.
Suggested change
| * Upgrades `dse-java-driver` to handle newer versions of Guava. (DSP-24191) | |
| * Upgraded `dse-java-driver` to handle newer versions of Guava. (DSP-24191) |
The release notes' guideline says that RN should start with a var in past tense, I think we should fix the remaining ones that do not follow this pattern too.
| * Fixed, observe spark.directJoin and spark.directJoinSizeRatio parameters. (DSP-24258) | ||
|
|
||
| ## 6.8.49 DSE Security | ||
| * Adds partial support for client and internode connections using TLSv1_3. (DSP-23989) |
There was a problem hiding this comment.
Suggested change
| * Adds partial support for client and internode connections using TLSv1_3. (DSP-23989) | |
| * Added partial support for client and internode connections using TLSv1_3. (DSP-23989) |
| If you're developing applications, please refer to the [Java Driver documentation](https://docs.datastax.com/en/driver-matrix/doc/java-drivers.html) to choose an appropriate version. | ||
|
|
||
| ## 6.8.49 DSE Core | ||
| * Prevents a Java driver request timeout for `drain()` operations executed via Management API by setting the request timeout to 0. The request timeout change only affects the internal Java driver used in Management API and is only set to 0 explicitly for the `drain()` operation. (DSP-23994) |
There was a problem hiding this comment.
Suggested change
| * Prevents a Java driver request timeout for `drain()` operations executed via Management API by setting the request timeout to 0. The request timeout change only affects the internal Java driver used in Management API and is only set to 0 explicitly for the `drain()` operation. (DSP-23994) | |
| * Prevented a Java driver request timeout for `drain()` operations executed via Management API by setting the request timeout to 0. The request timeout change only affects the internal Java driver used in Management API and is only set to 0 explicitly for the `drain()` operation. (DSP-23994) |
| * Prevents a Java driver request timeout for `drain()` operations executed via Management API by setting the request timeout to 0. The request timeout change only affects the internal Java driver used in Management API and is only set to 0 explicitly for the `drain()` operation. (DSP-23994) | ||
|
|
||
| ## 6.8.49 DSE Cassandra | ||
| * Secondary Index: Don't fail queries if one node is not available. (DSP-24163) |
There was a problem hiding this comment.
I would propose to phrase it a bit differently as currently it's difficult to guess what it does from the user perspective: how about Introduced a flag that allows skipping querying nodes that do not have ready secondary indexes". This behaviour can be enabled by setting -Ddse.cassandra.index.check_index_status=true? @roxananeo as the ticket author, what do you think?
|
Thx for the feedback @szymon-miezal next time I have to try to remember to review RN from all tickets. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release Notes Automation
If you name your pull-request as "Product x.y.z Release ...", after merging the
PR, a GitHub Action will automatically create a product version tag "product-x.y.z".
Supported product names are:
Version supports 3 sets or 4 sets of digits.