[
https://issues.apache.org/jira/browse/HDFS-6843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14114772#comment-14114772
]
Andrew Wang commented on HDFS-6843:
-----------------------------------
I'm aware, I did review the original FS contract patch :) The spec explicitly
says that it can be incomplete or incorrect, and that the in-code HDFS
implementation is the true spec. That indicated to me that updating the spec
*was not* a requirement for changes. Yes, in this case we just need to check a
boolean, but it could be a lot more work for other changes, and I don't want to
set a precedent that updating the spec is necessary.
Let's just take this to a follow-on JIRA?
> Create FSDataInputStream & FSDataOutputStream isEncrypted() method
> ------------------------------------------------------------------
>
> Key: HDFS-6843
> URL: https://issues.apache.org/jira/browse/HDFS-6843
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode, security
> Affects Versions: 3.0.0
> Reporter: Charles Lamb
> Assignee: Charles Lamb
> Attachments: HDFS-6843.001.patch, HDFS-6843.002.patch
>
>
> FileStatus should have a 'boolean isEncrypted()' method. (it was in the
> context of discussing with AndreW about FileStatus being a Writable).
> Having this method would allow MR JobSubmitter do the following:
> -----
> BOOLEAN intermediateEncryption = false
> IF jobconf.contains("mr.intermidate.encryption") THEN
> intermediateEncryption = jobConf.getBoolean("mr.intermidate.encryption")
> ELSE
> IF (I/O)Format INSTANCEOF File(I/O)Format THEN
> intermediateEncryption = ANY File(I/O)Format HAS a Path with status
> isEncrypted()==TRUE
> FI
> jobConf.setBoolean("mr.intermidate.encryption", intermediateEncryption)
> FI
--
This message was sent by Atlassian JIRA
(v6.2#6252)
