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

ASF subversion and git services commented on SQOOP-1203:
--------------------------------------------------------

Commit e187f454c550081687f72bedbd88d0a1d3d92f14 in branch refs/heads/trunk from 
[~jarcec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=e187f45 ]

SQOOP-1203: Add another default case for finding *_HOME when not explicitly 
defined

(Mark Grover via Jarek Jarcec Cecho)

                
> Add another default case for finding *_HOME when not explicitly defined 
> ------------------------------------------------------------------------
>
>                 Key: SQOOP-1203
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1203
>             Project: Sqoop
>          Issue Type: Improvement
>          Components: tools
>    Affects Versions: 1.4.4
>            Reporter: Mark Grover
>            Assignee: Mark Grover
>         Attachments: SQOOP-1203.1.patch
>
>
> Currently, the {{configure-sqoop}} scripts that checks the value of various 
> _HOME variables (e.g. HADOOP_MAPRED_HOME, HCAT_HOME, etc.) has the following 
> heuristic:
> 1. Use the *_HOME variable's value, if defined.
> 2. If not, assign /usr/lib/<relevant location> to the variable.
> 3. If /usr/lib/<relevant location> doesn't exist, error out
> I would like to propose to modify this to add one more case before we error 
> out.
> 1. Use the *_HOME variable's value, if defined.
> 2. If not, assign /usr/lib/<relevant location> to the *_HOME variable.
> 3. If /usr/lib/<relevant location> doesn't exist, check for hadoop and hcat 
> at the same directory level as sqoop
> 4. If #3 fails as well, error out.
> This is backwards compatible because it wouldn't be touching any of the 
> existing cases. It will just add more location to check for presence of 
> hadoop, hcat etc. before erroring out.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to