[
https://issues.apache.org/jira/browse/HADOOP-8101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242581#comment-13242581
]
Aaron T. Myers commented on HADOOP-8101:
----------------------------------------
bq. I think you mean the work done in HADOOP-8121. Can that be ported to this
branch if needed? When running on Windows, I think we might be able to get away
using Windows shell commands which use the built-in OS support (taking
advantage of the efficiency and caching provided by Windows).
I was indeed referring to HADOOP-8121. Sure, providing an implementation that
shells out could make sense too, though note that Hadoop itself has built-in
caching for user -> group mapping, so it might not make that much of a
difference from a performance perspective.
bq. I think, if I understand Sanjay's intent correctly, he is describing the
support needed in a non-secure (non-authenticated) Hadoop setup. Hence, the LTC
etc pieces are not yet in the picture. Sanjay, please correct me if needed.
Ah, my mistake. We might want to update the description of this JIRA to make it
clear exactly what the scope of this change is intended to be.
bq. As an aside, LTC (LinuxTaskController) is a pieces of native code that gets
executed on demand. If that abstraction is correct, it can be replicated for
Windows although it might make sense to revisit the abstraction.
Sure, makes sense.
> Security changes for Hadoop for Windows
> ---------------------------------------
>
> Key: HADOOP-8101
> URL: https://issues.apache.org/jira/browse/HADOOP-8101
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: native
> Reporter: Sanjay Radia
> Attachments: security.patch, security1.patch
>
>
--
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
