[
https://issues.apache.org/jira/browse/IGNITE-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814591#comment-15814591
]
Taras Ledkov edited comment on IGNITE-3667 at 1/10/17 10:23 AM:
----------------------------------------------------------------
HDFS uses the user parameter only for java security with JAAS. Ignite doesn't
work with java {{SecurityManager}}. So java security with {{FilePermission}} is
no applied for IGFS local secondary.
The operation with the native file systems are performed with process owner's
permissions (not supported by java, not supported by Ignite).
So hdfs doesn't set the default user for file operation.
Looks like the propagation of a user context is not necessary for IGFS local
secondary.
was (Author: tledkov-gridgain):
HDFS uses the user parameter only for java security with JAAS. Ignite doesn't
work with java {{SecurityManager}}. So java security with {{ FilePermission}}
is no applied for IGFS local secondary.
The operation with the native file systems are performed with process owner's
permissions (not supported by java, not supported by Ignite).
So hdfs doesn't set the default user for file operation.
Looks like the propagation of a user context is not necessary for IGFS local
secondary.
> IGFS: Local secondary: Ensure that user context is propagated properly to
> underlying FS operation.
> --------------------------------------------------------------------------------------------------
>
> Key: IGNITE-3667
> URL: https://issues.apache.org/jira/browse/IGNITE-3667
> Project: Ignite
> Issue Type: Task
> Components: IGFS
> Affects Versions: 1.6
> Reporter: Vladimir Ozerov
> Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> If operation was initiated by user X, then it should be processed on behalf
> of this user, not on behalf of Ignite process owner.
> See {{IgniteHadoopIgfsSecondaryFileSystem.fileSystemForUser()}} for reference.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
