[
https://issues.apache.org/jira/browse/HDFS-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859056#action_12859056
]
sam rash commented on HDFS-1102:
--------------------------------
well, it's not w/o modifying hftp, but a client can verify the content length
if it's there, and proceed as it does now if it's not present.
we could also have a config option that say "enforce content length" which
would cause missing content length => throw IOException.
in this way, if both the client and server are on the latest hftp, this works,
else it will work as before
offhand, i'm not sure how to do this without either changing hftp or wrapping
it in some other protocol that does length checking
> HftpFileSystem : errors during transfer result in truncated transfer
> --------------------------------------------------------------------
>
> Key: HDFS-1102
> URL: https://issues.apache.org/jira/browse/HDFS-1102
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: data-node, hdfs client
> Affects Versions: 0.20.1
> Reporter: sam rash
>
> If an error occurs transferring the data over HTTP, the HftpInputStream does
> not know it received fewer bytes than the file contains. We can at least
> detect this and throw an EOFException when this occurs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
