ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahadev konar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-7842) Ambari to manage tarballs on HDFS
Date Wed, 29 Oct 2014 02:35:34 GMT

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

Mahadev konar commented on AMBARI-7842:
---------------------------------------

+1 for the additional patch.

> Ambari to manage tarballs on HDFS
> ---------------------------------
>
>                 Key: AMBARI-7842
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7842
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>            Priority: Blocker
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-7842.patch, AMBARI-7842.v2.patch, AMBARI-7842_branch-1.7.0.patch,
ambari_170_versioned_rpms.pptx
>
>
> With HDP 2.2, Ambari needs to copy the tarballs/jars from the local file system to a
certain location in HDFS.
> The tarballs/jars no longer have a version number (either component version or HDP stack
version + build) in the name), but the destination folder in HDFS does contain the HDP Version
(e.g., 2.2.0.0-999).
> {code}
> /hdp/apps/$(hdp-stack-version)
>   |---- mapreduce/mapreduce.tar.gz
>   |---- mapreduce/hadoop-streaming.jar (which is needed by WebHcat. In the file system,
it is a symlink to a versioned file, so HDFS needs to follow the link)
>   |---- tez/tez.tar.gz
>   |---- pig/pig.tar.gz
>   |---- hive/hive.tar.gz
>   |---- sqoop/sqoop.tar.gz
> {code}
> Furthermore, the folders created in HDFS need to have a permission of 0555, while files
need 0444.
> The owner should be hdfs, and the group should be hadoop.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message