hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajiv Chittajallu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6978) Add JNI support for secure IO operations
Date Mon, 15 Nov 2010 21:58:14 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932216#action_12932216

Rajiv Chittajallu commented on HADOOP-6978:

bq. That seems fairly reasonable (adding a cache here). 

Systems generally have nscd or an equivalent to handle nss cache. I think we should leave
that uid/gid caching to underlying system.

Most of the getpw calls are for uid to username lookups since hadoop deals only with username.
Wouldn't it be simple to pass the uid along with the username when the JT hands off the task
to the tt?

> Add JNI support for secure IO operations
> ----------------------------------------
>                 Key: HADOOP-6978
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6978
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: io, native, security
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Critical
>             Fix For: 0.22.0
>         Attachments: hadoop-6978.txt, hadoop-6978.txt
> In support of MAPREDUCE-2096, we need to add some JNI functionality. In particular, we
need the ability to use fstat() on an open file stream, and to use open() with O_EXCL, O_NOFOLLOW,
and without O_CREAT.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message