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

Steve Loughran commented on HADOOP-15871:
-----------------------------------------

In S3A I'm going to have it return what the inner S3 stream says, returning "1" 
otherwise, which is what that inner stream does. I'm not going near HDFS I'm 
afraid

> Some input streams does not obey "java.io.InputStream.available" contract 
> --------------------------------------------------------------------------
>
>                 Key: HADOOP-15871
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15871
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs, fs/s3
>            Reporter: Shixiong Zhu
>            Priority: Major
>
> E.g,  DFSInputStream  and S3AInputStream return the size of the remaining 
> available bytes, but the javadoc of "available" says it should "Returns an 
> estimate of the number of bytes that can be read (or skipped over) from this 
> input stream *without blocking* by the next invocation of a method for this 
> input stream."
> I understand that some applications may rely on the current behavior. It 
> would be great that there is an interface to document how "available" should 
> be implemented.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to