[
https://issues.apache.org/jira/browse/NIFI-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15376159#comment-15376159
]
ASF GitHub Bot commented on NIFI-2026:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/475
Since other Apache projects are taking the stance of including the
repositories in the top-level POM, I think NiFi should too. These would include
(at a minimum) the MapR, Cloudera, and Hortonworks repositories. However IMO we
should the draw the line at profiles, and instead enable variables like
hadoop.version, hive.version, etc. and add a Wiki page or some other form of
community documentation showing how to build a vendor-specific distribution of
NiFi. Thoughts?
> nifi-hadoop-libraries-nar should use profiles to point to different hadoop
> distro artifacts
> -------------------------------------------------------------------------------------------
>
> Key: NIFI-2026
> URL: https://issues.apache.org/jira/browse/NIFI-2026
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Andre
>
> Raising a JIRA issue as discussed with [~mattyb149] as part of PR-475.
> Users using particular Hadoop versions may struggle to use *HDFS against a
> cluster running proprietary or particular versions of HDFS.
> Therefore, until we find a cleaner way of BYO hadoop machanism (as suggested
> in NIFI-710), we should consider introducing a maven profiles to support
> different hadoop library, enabling users to compile.
> This should cause no changes to default behaviour, just eliminating the need
> to clone, modify, build and copy NAR bundles over standard NiFi artifacts.
> Unless the profile is explicitly requested, build will still includes just
> the Apache licensed artifacts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
