[ 
https://issues.apache.org/jira/browse/HBASE-10255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13858931#comment-13858931
 ] 

Ted Yu commented on HBASE-10255:
--------------------------------

bq. there there was a wrong-headed attempt at adding a guava class to hbase 
core.
The checkin of 
hbase-common/src/main/java/org/apache/hadoop/hbase/io/LimitInputStream.java was 
not done in HBASE-10174.

I was just addressing your review comments. The priority of this JIRA was set 
according to the tone of your comment from HBASE-10174.

bq. on issues that it is easy to discern how they move the project forward.
Understood your point. I have helped in producing 0.98 release. See the 
following example where Andrew spent much time hunting down the cause:
HBASE-10142 TestLogRolling#testLogRollOnDatanodeDeath test failure

> Remove dependency on LimitInputStream
> -------------------------------------
>
>                 Key: HBASE-10255
>                 URL: https://issues.apache.org/jira/browse/HBASE-10255
>             Project: HBase
>          Issue Type: Task
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>            Priority: Minor
>             Fix For: 0.98.0, 0.99.0
>
>         Attachments: 10255-v1.txt, 10255-v2.txt
>
>
> LimitInputStream has always been a @Beta API and beta apis aren't guaranteed 
> to remain stable over such a long period (v12 to v15).
> LimitInputStream was copied from Guava v12
> The recommended replacement is to use ByteStreams#limit(java.io.InputStream, 
> long) instead.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to