You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2012/07/04 23:50:55 UTC

[jira] [Updated] (AMBARI-544) Templeton configs for pig archive not correct in HMC

     [ https://issues.apache.org/jira/browse/AMBARI-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli updated AMBARI-544:
-------------------------------------------

    Fix Version/s: 0.9.0
    
> Templeton configs for pig archive not correct in HMC
> ----------------------------------------------------
>
>                 Key: AMBARI-544
>                 URL: https://issues.apache.org/jira/browse/AMBARI-544
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: ambari-186
>            Reporter: Ramya Sunil
>            Assignee: Ramya Sunil
>             Fix For: 0.9.0
>
>         Attachments: ambari-544.patch
>
>
> From Arpit:
> The configs for pig in templeton are wrong.
> The deployed configs are
> {noformat}
> <property>
>     <name>templeton.pig.archive</name>
>     <value>hdfs:///apps/templeton/</value>
>     <description>The path to the Pig archive.</description>
>   </property>
>   <property>
>     <name>templeton.pig.path</name>
>     <value>/pig-0.9.2/bin/pig</value>
>     <description>The path to the Pig executable.</description>
>   </property>
> {noformat}
> They are missing the pig tar ball. For example they should be
> {noformat}
> <property>
>     <name>templeton.pig.archive</name>
>     <value>hdfs:///apps/templeton/pig.tar.gz</value>
>     <description>The path to the Pig archive.</description>
>   </property>
>   <property>
>     <name>templeton.pig.path</name>
>     <value>pig.tar.gz/pig-0.9.2/bin/pig</value>
>     <description>The path to the Pig executable.</description>
>   </property>
> {noformat}
> So both the properties are missing 'pig-0.9.2.tar.gz'

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira