[
https://issues.apache.org/jira/browse/HADOOP-15871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943098#comment-16943098
]
Steve Loughran commented on HADOOP-15871:
-----------------------------------------
just looked at ABFS input streams here:
{code:java}
*
* This is to match the behavior of DFSInputStream.available(),
* which some clients may rely on (HBase write-ahead log reading in
* particular)."
{code}
If that is true (and given the gzip issues) I'm going to have to make this a
WONTFIX. Sorry
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
