[
https://issues.apache.org/jira/browse/NIFI-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15376303#comment-15376303
]
ASF GitHub Bot commented on NIFI-2026:
--------------------------------------
Github user tdunning commented on the issue:
https://github.com/apache/nifi/pull/475
I got mentioned a few responses ago, so I feel that I ought to answer.
Either approach to supporting different distributions is a really good idea
since it makes it easier for users, but doesn't impinge on the developers in
any important way. Whether profiles are used for this or just repositories with
versions selected by the users is pretty much a toss-up (from the user's point
of view).
One of the major tenets of Apache is business friendly open source, so
facilitating consumption of Apache software in this way by vendors (who really
do add lots of value, frankly) is very much aligned with core Apache goals.
> 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)
