[
https://issues.apache.org/jira/browse/SQOOP-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14341072#comment-14341072
]
Mark Grover commented on SQOOP-2145:
------------------------------------
It is, but this makes the out of box experience better, it's like having 2
defaults. If one doesn't work, we try the second one, and if that doesn't work
either we give up. Currently, we have only one default for hive. For hcatalog,
for example, we have 2 defaults, and it makes the experience much more seemless.
> 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)
