[
https://issues.apache.org/jira/browse/NIFI-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15408225#comment-15408225
]
ASF subversion and git services commented on NIFI-2435:
-------------------------------------------------------
Commit f46ea411e13db458136550019bcd6bb2748037b0 in nifi's branch refs/heads/0.x
from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=f46ea41 ]
NIFI-2435 - Wrapping reader call in doAs if necessary
This closes #780.
Signed-off-by: Bryan Bende <[email protected]>
> GetHDFSSequenceFile sequence reader throwing away authenticated filesystem
> and creating its own
> -----------------------------------------------------------------------------------------------
>
> Key: NIFI-2435
> URL: https://issues.apache.org/jira/browse/NIFI-2435
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.6.1
> Environment: Kerberos HDFS
> Reporter: Juan Sequeiros
> Assignee: Bryan Rosander
> Labels: hdfs, kerberos
> Fix For: 1.0.0, 0.7.1
>
>
> Hadoop Kerberos has a way of accessing things as an authenticated user
> UserGroupInformation.doAs
> NIFI is doing that to get access to the filesystem in order to basically
> tell hadoop to use the correct credentials so our processor does that
> correctly and then passes the results into the sequence reader unfortunately,
> the sequence reader then throws away our authenticated filesystem and creates
> its own without wrapping in a UGI.doAs
> More context:
> The constructor used for org.apache.hadoop.io.SequenceFile.Reader in both
> KeyValueReader and ValueReader is deprecated and has been turned into a
> callthrough that only uses the passed in FileSystem to get the qualified
> path[1]. I've modified those classes to do that logic and then wrapped the
> callsite in the processor in a UGI.doAs if it is configured to use a UGI
> [1]:
> https://github.com/apache/hadoop/commit/0c462b223f151208ff7bd5148cee0e436c23d795#diff-e70823f17863445da52875999e4b19a2L1592
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
