Github user joaocc commented on the issue:
https://github.com/apache/nifi/pull/399
@simonellistonball Hi. Was the work on Azure Storage Table dropped? I tried
to find it in the current (1.8) version but only Storage Blob seems to be
there. Thx
---
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/399
@simonellistonball - Seems like your PR has been adopted by @jtstorck and
@aperepel so closing this PR as we currently have 3 PRs for the same JIRA.
---
If your project is set up for it, you can repl
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/399
@slachterman - thank you for the handy link
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
en
Github user slachterman commented on the issue:
https://github.com/apache/nifi/pull/399
Example for Azure Data Lake Storage using additional classpath
functionality:
https://community.hortonworks.com/articles/58793/hdf-20-use-ambari-to-enable-kerberos-for-hdf-clust.html
---
If your
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/399
@simonellistonball can you consider closing this in favor of the approach
outlined in NIFI-1922 which takes advantage of a new runtime classpath
manipulation option which has been proven to work.
---
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/399
@slachterman I would say so
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user slachterman commented on the issue:
https://github.com/apache/nifi/pull/399
Quick question: is there overlap with
[NIFI-1922](https://issues.apache.org/jira/browse/NIFI-1922)?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user simonellistonball commented on the issue:
https://github.com/apache/nifi/pull/399
Latest commit should remove some of the duplicate nar circular dependency
issues. It's not the cleanest way to implement this, but that really wants a
common cloud util library around the way
