nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-2026) nifi-hadoop-libraries-nar should use profiles to point to different hadoop distro artifacts
Date Wed, 15 Jun 2016 13:09:09 GMT

    [ https://issues.apache.org/jira/browse/NIFI-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15331705#comment-15331705
] 

ASF GitHub Bot commented on NIFI-2026:
--------------------------------------

Github user mattyb149 commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/475#discussion_r67157439
  
    --- Diff: nifi-assembly/pom.xml ---
    @@ -470,6 +470,15 @@ language governing permissions and limitations under the License.
-->
         </properties>
         <profiles>
             <profile>
    +            <id>mapr</id>
    --- End diff --
    
    Seems like with the addition of the custom_hadoop_libraries profile and the nifi.hadoop.distro.params,
we don't need this explicit profile anymore (or it should be renamed to match the one in the
NAR)? I like the generic profile/options versus anything vendor-specific


> 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)

Mime
View raw message