[
https://issues.apache.org/jira/browse/NIFI-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878573#comment-15878573
]
ASF GitHub Bot commented on NIFI-385:
-------------------------------------
GitHub user WilliamNouet opened a pull request:
https://github.com/apache/nifi/pull/1528
NIFI-385 Add Kerberos support in nifi-kite-nar
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] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [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 master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1528.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 #1528
----
commit 41dbe81edae792dca3074007030a0623a331a2de
Author: WilliamNouet <[email protected]>
Date: 2017-02-22T15:05:30Z
[NIFI-385] Add Kerberos support in nifi-kite-nar
commit 204153c7f6266947211c924388685944a82cad33
Author: WilliamNouet <[email protected]>
Date: 2017-02-22T15:07:38Z
Update AbstractKiteProcessor.java
commit 1a844903bee2e8ed7e70097b79ca33c640343d8a
Author: WilliamNouet <[email protected]>
Date: 2017-02-22T15:14:23Z
Update ConvertCSVToAvro.java
Taking into account AbtractKiteProcessor changes
commit 8fa42cf3f6b134f4eb7bc3da46582bc80d72ccfb
Author: WilliamNouet <[email protected]>
Date: 2017-02-22T15:17:22Z
Update ConvertJSONToAvro.java
Taking into account changes from AbstractKiteProcessor
commit 4789836592831cbd8228cdd2ac8b6dbad6811660
Author: WilliamNouet <[email protected]>
Date: 2017-02-22T15:26:41Z
Update StoreInKiteDataset.java
Core of the changes for [NIFI-385]
commit 6670b2643fa9359245873d1107afd6e9d1a829c6
Author: WilliamNouet <[email protected]>
Date: 2017-02-22T15:37:40Z
Update pom.xml
commit d47c92fbe3eba12a73407bc7608e3146a457804f
Author: WilliamNouet <[email protected]>
Date: 2017-02-22T15:41:43Z
Merge pull request #1 from WilliamNouet/NIFI-385
[NIFI-385] Add Kerberos support in nifi-kite-nar
----
> 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.3.15#6346)
