[ 
https://issues.apache.org/jira/browse/HDDS-11768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Andika updated HDDS-11768:
-------------------------------
    Description: 
There are a lot of duplicated SCM proxy provider logic in
 * SCMBlockLocationFailoverProxyProvider
 * SCMContainerLocationFailoverProxyProvider
 * SCMSecurityProtocolFailoverProxyProvider
 * SecretKeyProtocolFailoverProxyProvider
 * SingleSecretKeyProtocolProxyProvider

It's better to extract the logic to a separate class (e.g parent class) to 
prevent divergent implementation of this critical logic.

  was:
There are a lot of duplicated SCM proxy provider logic in
 * SCMBlockLocationFailoverProxyProvider
 * SCMContainerLocationFailoverProxyProvider
 * SCMSecurityProtocolFailoverProxyProvider
 * SecretKeyProtocolFailoverProxyProvider
 * SingleSecretKeyProtocolProxyProvider

It's better to extract the logic to a separate class (e.g parent class).


> Extract SCM failover proxy provider logic
> -----------------------------------------
>
>                 Key: HDDS-11768
>                 URL: https://issues.apache.org/jira/browse/HDDS-11768
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: SCM Client
>            Reporter: Ivan Andika
>            Priority: Major
>
> There are a lot of duplicated SCM proxy provider logic in
>  * SCMBlockLocationFailoverProxyProvider
>  * SCMContainerLocationFailoverProxyProvider
>  * SCMSecurityProtocolFailoverProxyProvider
>  * SecretKeyProtocolFailoverProxyProvider
>  * SingleSecretKeyProtocolProxyProvider
> It's better to extract the logic to a separate class (e.g parent class) to 
> prevent divergent implementation of this critical logic.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to