ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay Srinivasaraghavan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-8947) Tez and Mapred tarballs are not copied to the default FS when fs.defaultFs is not hdfs:///
Date Wed, 18 Mar 2015 06:38:38 GMT

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

Vijay Srinivasaraghavan commented on AMBARI-8947:
-------------------------------------------------

If we keep the URI namespace to be generic say "hcfs" for all the tarball copy path and have
the corresponding FS stack define a placeholder in the cluster-env. The dynamic_variable_interpretation.py
script can be modified to dynamically apply the placeholder as replacement value for "hcfs".
This allows any FS stack provider to support storing versioned tarballs. 

Please see AMBARI-10023 for more details. 

https://issues.apache.org/jira/secure/attachment/12703841/HCFS-Integration-Design%20Draft%201.pdf
- Point 5 talks about the tarball scenario. 

> Tez and Mapred tarballs are not copied to the default FS when fs.defaultFs is not hdfs:///
> ------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-8947
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8947
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Ivan Mitic
>            Assignee: Ivan Mitic
>              Labels: HDP
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-8947.patch
>
>
> There is an assumption in {{dynamic_variable_interpretation.py}} that the default FS
is hdfs which prevent tarballs from being copied with other file systems. 



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

Mime
View raw message