[
https://issues.apache.org/jira/browse/HADOOP-6605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037110#comment-13037110
]
Chris Douglas commented on HADOOP-6605:
---------------------------------------
This struck me as an obvious win, but I'm starting to see Allen's point.
Incomplete detection may save some users a couple minutes, but it will cause
weird bugs in other systems. The globbing/non-Sun JVM cases are especially
salient. The benefit is clear to anyone who's set this variable dozens (if not
hundreds) of times, but the potential cost is more subtle. As automatic
behavior, this is trying to be too clever for a nominal benefit.
That said, the MacOS tool seems designed to accomplish _exactly_ this, and I'd
have no problem if it were to show up in the script. If it stops being a
reliable way of setting {{JAVA_HOME}}, we'll just fix it. If there are similar
tools in Solaris/Linux (doesn't {{/etc/alternatives}} support similar
functionality?), we can make use of them.
> Add JAVA_HOME detection to hadoop-config
> ----------------------------------------
>
> Key: HADOOP-6605
> URL: https://issues.apache.org/jira/browse/HADOOP-6605
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Chad Metcalf
> Assignee: Eli Collins
> Priority: Minor
> Fix For: 0.22.0
>
> Attachments: HADOOP-6605.patch, hadoop-6605-1.patch,
> hadoop-6605-2.patch
>
>
> The commands that source hadoop-config.sh currently bail with an error if
> JAVA_HOME is not set. Let's detect JAVA_HOME (from a list of locations on
> various OS types) if JAVA_HOME is not already set by hadoop-env.sh or the
> environment. This way users don't have to manually configure it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
