SPARKC-683 Bump up DSE & OSS C* versions the latest - #1346
Open
msmygit wants to merge 1 commit into
Open
Conversation
msmygit
changed the title
msmygit
marked this pull request as ready for review
June 22, 2022 20:12
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
SPARKC-683 Bump up DSE & OSS C* versions the latest
How did the Spark Cassandra Connector Work or Not Work Before this Patch
SCC was testing with older DSE & OSS C* version prior to this patch
Describe the problem, or state of the project that this patch fixes. Explain
why this is a problem if this isn't obvious.
Not a big problem at this point, but it would be better to test with the latest patch versions of the base database.
General Design of the patch
DSE & OSS C* versions are bumped in the GitHub workflows.
There is no ticket for it as of now.
How Has This Been Tested?
Almost all changes and especially bug fixes will require a test to be added to either the integration or Unit Tests. Any tests added will be automatically run on travis when the pull request is pushed to github. Be sure to run suites locally as well.
Checklist: