HDDS-4298. Use an interface in Ozone client instead of XceiverClientManager #1460
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.
What changes were proposed in this pull request?
XceiverClientManageris used everywhere in the ozone client (Key/Block Input/OutputStream) to get a client when required.To make it easier to create genesis/real unit tests, it would be better to use a generic interface instead of
XceiverClientManagerwhich can be replaced easily with a mock implementation.What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4298
How was this patch tested?
Usability: Created a real unit test (mocked-read branch on my fork) for HDDS-4285.
Correctness: CI
(this is a very simple change, I just introduced a new interface and Input/Ouptut streams use the interface instead of the implementation)