Refactor CQLSessionCache and CqlCredentials #1455
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
needed a way to get a session using only the (String tenantId, String authToken) and the way the cache key worked made they very hard / impossible. Also the code needed a refactor. Needed the new access technique for the OperationAttempt where we are trying to stop carrying the DataApiRequestInfo everywhere as it's IOC pattern mixes application and requests state (and generally to remove the IOC injection)
tatu-at-datastax
approved these changes
Sep 26, 2024
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.
needed a way to get a session using only the
(String tenantId, String authToken) and the way the cache key worked made they very hard / impossible. Also the code needed a refactor.
Needed the new access technique for the OperationAttempt where we are trying to stop carrying the DataApiRequestInfo everywhere as it's IOC pattern mixes application and requests state (and generally to remove the IOC injection)
What this PR does:
Which issue(s) this PR fixes:
Fixes #
Checklist