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

Andrew Purtell updated HBASE-15982:
-----------------------------------
    Description: 
We have Guava's Service leaking into the LimitedPrivate interface 
ReplicationEndpoint:
{code}
public interface ReplicationEndpoint extends Service, 
ReplicationPeerConfigListener
{code}
This required a private patch when I updated Guava for our internal 
deployments. LP is only less than public by a degree. We shouldn't leak types 
from third part code into either Public or LP APIs in my opinion. Let's fix.

  was:
We have Guava's Service leaking into the LimitedPrivate interface 
ReplicationEndpoint:
{code
public interface ReplicationEndpoint extends Service, 
ReplicationPeerConfigListener
{code}
This required a private patch when I updated Guava for our internal 
deployments. LP is only less than public by a degree. We shouldn't leak types 
from third part code into either Public or LP APIs in my opinion. Let's fix.


> Interface ReplicationEndpoint extends Guava's Service
> -----------------------------------------------------
>
>                 Key: HBASE-15982
>                 URL: https://issues.apache.org/jira/browse/HBASE-15982
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Andrew Purtell
>             Fix For: 2.0.0, 1.3.0, 0.98.21
>
>
> We have Guava's Service leaking into the LimitedPrivate interface 
> ReplicationEndpoint:
> {code}
> public interface ReplicationEndpoint extends Service, 
> ReplicationPeerConfigListener
> {code}
> This required a private patch when I updated Guava for our internal 
> deployments. LP is only less than public by a degree. We shouldn't leak types 
> from third part code into either Public or LP APIs in my opinion. Let's fix.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to