hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vihang Karajgaonkar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-21484) Metastore API getVersion() should return real version
Date Wed, 27 Mar 2019 17:41:00 GMT

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

Vihang Karajgaonkar commented on HIVE-21484:
--------------------------------------------

Hi [~ngangam] Sorry for not getting back earlier. In my opinion schema version of the db is
a implementation detail which end users should not be exposed to. So having the source code
(project version) exposed it more reasonable since it can be tied with the APIs easily in
the future.

> Metastore API getVersion() should return real version
> -----------------------------------------------------
>
>                 Key: HIVE-21484
>                 URL: https://issues.apache.org/jira/browse/HIVE-21484
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Vihang Karajgaonkar
>            Assignee: Vihang Karajgaonkar
>            Priority: Minor
>         Attachments: HIVE-21484.01.patch
>
>
> Currently I see the {{getVersion}} implementation in the metastore is returning a hard-coded
"3.0". It would be good to return the real version of the metastore server using {{HiveversionInfo}}
so that clients can take certain actions based on metastore server versions.
> Possible use-cases are:
> 1. Client A can make use of new features introduced in given Metastore version else stick
to the base functionality.
> 2. This version number  can be used to do a version handshake between client and server
in the future to improve our cross-version compatibity story.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message