[
https://issues.apache.org/jira/browse/HDFS-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611357#comment-13611357
]
Todd Lipcon commented on HDFS-4538:
-----------------------------------
Took a look at the latest patch. I think the test coverage is still lacking --
the reason to add back this code path is for the Windows branch, where we have
no implementation of 347. In that case, you would configure _only_ the legacy,
and _not_ the new implementation nor a socket path. We need a test case that
covers this, but the test case in this patch seems to be checking a fallback
path instead.
> allow use of legacy blockreader
> -------------------------------
>
> Key: HDFS-4538
> URL: https://issues.apache.org/jira/browse/HDFS-4538
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: datanode, hdfs-client, performance
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Attachments: HDFS-4538.001.patch, HDFS-4538.002.patch,
> HDFS-4538.003.patch
>
>
> Some users might want to use the legacy block reader, because it is available
> on Windows, whereas the secure solution has not yet been implemented there.
> As described in the mailing list discussion, let's enable this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
