[
https://issues.apache.org/jira/browse/HADOOP-8319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268667#comment-13268667
]
Daryn Sharp commented on HADOOP-8319:
-------------------------------------
bq. The reason setWriteChecksum requires a patch argument is because
FileContext, just like ViewFS, works on paths and resolves the path to an FS.
If we remove the path, setWriteChecksum will have the side effect that it apply
to all the FS that the filecontext resolves in a path.
The side-effect is the very solution to the bug. If I tell my context:
"disable writing checksums because I really don't care about integrity", then I
implicitly don't care where the data is being written by the context. With the
patch as-is, the user can't reliably control the writing or verification of
checksums w/o explicitly resolving paths and creating a new context for the
resolved path -- which kind of defeats the purpose of the context.
Do you have another solution in mind to control the flags?
> FileContext does not support setWriteChecksum
> ---------------------------------------------
>
> Key: HADOOP-8319
> URL: https://issues.apache.org/jira/browse/HADOOP-8319
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 2.0.0, 3.0.0
> Reporter: John George
> Assignee: John George
> Attachments: HADOOP-8319.patch, HADOOP-8319.patch, HADOOP-8319.patch,
> HADOOP-8319.patch, HADOOP-8319.patch
>
>
> File Context does not support setWriteChecksum and hence users trying
> to use this functionality fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
