-
Notifications
You must be signed in to change notification settings - Fork 673
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.
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
SOLR-17516: LBHttpSolrClient: support HttpJdkSolrClient (Generic Version) #2828
Merged
Merged
Changes from all commits
Commits
Show all changes
26 commits
Select commit
Hold shift + click to select a range
c7e306c
Add additional unit tests
jdyer1 eae31a7
Both test classes to use same naming convention and in same package
jdyer1 ec026e2
- Randomly use either http client delegate in integration test
jdyer1 87bf82d
Use Self Signed Cert-Friendy SSL Context in Integration Test
jdyer1 898977a
Make LBHttp2SolrClient Generic
jdyer1 5200329
cleanup
jdyer1 025a6c0
tidy
jdyer1 392cde2
add license header
jdyer1 565cfad
cleanup
jdyer1 4c4c975
Merge branch 'main' into feature/SOLR-17516-c
jdyer1 2aba104
javadoc adjustment
jdyer1 8096039
tidy
jdyer1 b241c10
Small JavaDoc improvement
jdyer1 9df2df7
tidy
jdyer1 2d3449d
- LBSolrClient to catch treat IOException same as if wrapped in SolrS…
jdyer1 0f040b2
tidy
jdyer1 c6d3509
Merge branch 'main' into feature/SOLR-17516-c
jdyer1 0526351
refactoring to allow jdk client to partcipate in changes
jdyer1 6db4f75
Revert "refactoring to allow jdk client to partcipate in changes"
jdyer1 be8c973
Merge branch 'main' into feature/SOLR-17516-c
jdyer1 311d85a
fix test after merge
jdyer1 d725daf
Exception for HttpJdkSolrClient in LBSolrClient
jdyer1 f3bc8e0
tidy
jdyer1 551d03c
add missing override
jdyer1 01d139f
Merge branch 'main' into feature/SOLR-17516-c
jdyer1 037c994
CHANGES.txt
jdyer1 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a shame to see duplication in getRootCause IOException detection with the dedicated clause. Maybe it'd be cleaner to have another try-catch just around calling request() above that detects the IOException and throws it? Just a thought; I leave it to you.