You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/07/21 16:47:00 UTC
[jira] [Commented] (NIFI-385) Add Kerberos support in nifi-kite-nar
[ https://issues.apache.org/jira/browse/NIFI-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096473#comment-16096473 ]
ASF GitHub Bot commented on NIFI-385:
-------------------------------------
GitHub user WilliamNouet opened a pull request:
https://github.com/apache/nifi/pull/2029
NIFI-385 Add Kerberos Support to Kite
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
[Y] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
[Y] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[Y] Has your PR been rebased against the latest commit within the target branch (typically master)?
[Y] Is your initial contribution a single, squashed commit?
For code changes:
[Y] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[Y] Have you written or updated unit tests to verify your changes?
[N/A] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[N/A] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[N/A] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[N/A] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?
For documentation related changes:
[N/A] Have you ensured that format looks appropriate for the output in which it is rendered?
Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/WilliamNouet/nifi NIFI-385
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/2029.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 #2029
----
commit 79322c32537d98b83f3a432f298ac04b1c54cffe
Author: WilliamNouet <wi...@berkeley.edu>
Date: 2017-07-21T16:44:31Z
NIFI-385 Add Kerberos Support to Kite
----
> Add Kerberos support in nifi-kite-nar
> -------------------------------------
>
> Key: NIFI-385
> URL: https://issues.apache.org/jira/browse/NIFI-385
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Ryan Blue
>
> Kite should be able to connect to a Kerberized Hadoop cluster to store data. Kite's Flume connector has working code. The Kite dataset needs to be instantiated in a {{doPrivileged}} block and its internal {{FileSystem}} object will hold the credentials after that.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)