[
https://issues.apache.org/jira/browse/IMPALA-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailesh Mukil resolved IMPALA-4744.
-----------------------------------
Resolution: Fixed
Fix Version/s: Impala 2.13.0
Impala 3.0
Thanks [~jbapple]. Updated:
https://cwiki.apache.org/confluence/display/IMPALA/How+to+Release
Closing this.
> Apache Impala release should include release tag or hash in version string
> --------------------------------------------------------------------------
>
> Key: IMPALA-4744
> URL: https://issues.apache.org/jira/browse/IMPALA-4744
> Project: IMPALA
> Issue Type: Improvement
> Components: Infrastructure
> Affects Versions: Impala 2.8.0
> Reporter: Tim Armstrong
> Assignee: Sailesh Mukil
> Priority: Major
> Fix For: Impala 3.0, Impala 2.13.0
>
>
> If I build the Apache Impala release from a source tarball, I get this
> version string:
> {code}
> tarmstrong@tarmstrong-box:~/apache-impala-incubating-2.8.0/apache-impala-incubating-2.8.0$
> impala-shell.sh
> INFO:bootstrap_virtualenv:Installing Kudu into the virtualenv
> Starting Impala Shell without Kerberos authentication
> Connected to localhost:21000
> Server version: impalad version 2.8.0-RELEASE DEBUG (build Could not obtain
> git hash)
> {code}
> It would be nice if we had a way to put something more friendly in there,
> e.g. the release tag or the git hash.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
