[
https://issues.apache.org/jira/browse/HIVE-29324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhihua Deng updated HIVE-29324:
-------------------------------
Description: In [https://github.com/apache/hive/blob/master/bin/hive#L302,]
we check the Hadoop version by default, this sounds outdated. As of now the
Hive binary doesn't include Hadoop jars, it relies on outer deployment to tell
where the Hadoop is, and if we chance the log output, Hive command might fail
because of unable to parse the version, brings some maintenance overhead.
(was: In [https://github.com/apache/hive/blob/master/bin/hive#L302,] we check
the Hadoop version by default, this sounds outdated. As of now the Hive binary
doesn't include Hadoop jars, it relies on outer deployment to tell where the
Hadoop is, and if we chance the log output, this command might fail because of
unable to parse the version, brings some maintenance overhead.)
> Remove the legacy Hadoop version check
> --------------------------------------
>
> Key: HIVE-29324
> URL: https://issues.apache.org/jira/browse/HIVE-29324
> Project: Hive
> Issue Type: Improvement
> Reporter: Zhihua Deng
> Priority: Minor
>
> In [https://github.com/apache/hive/blob/master/bin/hive#L302,] we check the
> Hadoop version by default, this sounds outdated. As of now the Hive binary
> doesn't include Hadoop jars, it relies on outer deployment to tell where the
> Hadoop is, and if we chance the log output, Hive command might fail because
> of unable to parse the version, brings some maintenance overhead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
