[ 
https://issues.apache.org/jira/browse/NIFI-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406577#comment-15406577
 ] 

ASF GitHub Bot commented on NIFI-2435:
--------------------------------------

GitHub user brosander opened a pull request:

    https://github.com/apache/nifi/pull/780

    NIFI-2435 - Wrapping reader call in doAs if necessary

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/brosander/nifi NIFI-2435-master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/780.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #780
    
----
commit 43a26698f9941f0732315f3e36d1fd2d3393f0d1
Author: Bryan Rosander <[email protected]>
Date:   2016-08-03T18:02:52Z

    NIFI-2435 - Wrapping reader call in doAs if necessary

----


> 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
>
> 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



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

Reply via email to