ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Veselovsky (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-761) User context set via ugi.doAs() is not always passed to 2ndary fs of IgniteHadoopFileSystem created in the same process
Date Thu, 16 Apr 2015 22:08:58 GMT
Ivan Veselovsky created IGNITE-761:
--------------------------------------

             Summary: User context set via ugi.doAs() is not always passed to 2ndary fs of
IgniteHadoopFileSystem created in the same process
                 Key: IGNITE-761
                 URL: https://issues.apache.org/jira/browse/IGNITE-761
             Project: Ignite
          Issue Type: Task
          Components: hadoop
            Reporter: Ivan Veselovsky
            Assignee: Ivan Veselovsky


Spawned from https://issues.apache.org/jira/browse/IGNITE-218 :
When a mapred task is working in Ignite node, it may access IgniteHadoopFileSystem, which,
in turn, may have a secondary file system.
Solving the issue 218 we tried to pass the user context of the mapred task using standard
Hadoop mechanism ugi.doAs().
But experiments show that this user context is not always correctly passed to the IgniteHadoopFileSystem
constructor.
Preliminary investigation shows that Principal list got from the Subject are empty. This happens
because the principal list is got by class key, in case  of Hadoop this is User.class. But
if the caller class "User.class" is loaded by another classloader, that class is not identical
to the class "User.class" that was used upon Principal creation, so the returned list is empty.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message