You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Mark Grover (JIRA)" <ji...@apache.org> on 2015/02/28 00:06:07 UTC

[jira] [Comment Edited] (SQOOP-2145) Default Hive home is not being set properly under certain circumstances

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

Mark Grover edited comment on SQOOP-2145 at 2/27/15 11:05 PM:
--------------------------------------------------------------

Tested the patch on my tarball based cluster.


was (Author: mgrover):
Tested it on my tarball based cluster.

> Default Hive home is not being set properly under certain circumstances
> -----------------------------------------------------------------------
>
>                 Key: SQOOP-2145
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2145
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.4.6
>            Reporter: Mark Grover
>            Assignee: Mark Grover
>             Fix For: 1.4.6
>
>         Attachments: SQOOP-2145.1.patch
>
>
> Currently, we have a bunch of _HOME defaults that are detected in bin/configure-sqoop. However, HIVE_HOME is not there. The only default for HIVE_HOME is hardcoded in java at https://github.com/apache/sqoop/blob/trunk/src/java/org/apache/sqoop/SqoopOptions.java#L64
> and that's not enough. The reason is often times people have tarballs like 
> ~/sqoop, ~/hive, etc. and it would be good to have their hive import jobs work out of the book. It makes sense to add some smartness (we already have that for other components like hcatalog) related to HIVE_HOME in configure-sqoop.
> This doesn't regress anything because it only sets the HIVE_HOME if it's not already set and the directory it's setting it to exists and is valid.



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