You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2014/10/25 19:49:34 UTC
[jira] [Resolved] (AMBARI-7970) if templeton.sqoop.archive is set
templeton.sqoop.home must be set as well
[ https://issues.apache.org/jira/browse/AMBARI-7970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitry Lysnichenko resolved AMBARI-7970.
----------------------------------------
Resolution: Fixed
Committed to trunk and to branch-1.7.0
> if templeton.sqoop.archive is set templeton.sqoop.home must be set as well
> --------------------------------------------------------------------------
>
> Key: AMBARI-7970
> URL: https://issues.apache.org/jira/browse/AMBARI-7970
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 1.7.0
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-7970.patch
>
>
> There are 3 properties in webhcat-site.xml related to Sqoop.
> templeton.sqoop.archive and templeton.sqoop.path are old properties (Baikal timeframe, so I assume Ambari already supports them)
> templeton.sqoop.home which needs to be set if (and only if) templeton.sqoop.archive is set.
> templeton.sqoop.home works the same way as templeton.hcat.home and templeton.hive.home.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)