You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2017/11/17 15:02:00 UTC

[jira] [Commented] (AMBARI-22467) YARN, MapReduce2, Hive, and Oozie Should Conditionally Install LZO

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

Hadoop QA commented on AMBARI-22467:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12898215/AMBARI-22467.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12686//console

This message is automatically generated.

> YARN, MapReduce2, Hive, and Oozie Should Conditionally Install LZO
> ------------------------------------------------------------------
>
>                 Key: AMBARI-22467
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22467
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.6.1
>
>         Attachments: AMBARI-22467.patch
>
>
> Changes Summary:
> - Do not install lzo if GPL license if not accepted, instead give out logger.warning and skip
> - Remove installation of lzo from metainfo.xml. Since we need to install lzo on restart if lzo is enabled/license accepted, we still need to do this in Python code. No need to duplicate.
> Clients will also use that code during install.
> - Move function get_lzo_packages to lzo_utils.py
> - Add code for Yarn, MR2, Hive to install lzo, edit existing code to install lzo for HDFS,Oozie to use lzo_utils.py 
> Notes:
> - Impl is Patch Upgrade friendly as uses the same code to detect {stack_version} as all the other packages. That code (not implemented here) gets version depending component specific repo info not stack specific.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)