hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naveen Gangam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-21484) Metastore API getVersion() should return real version
Date Thu, 21 Mar 2019 13:43:00 GMT

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

Naveen Gangam commented on HIVE-21484:
--------------------------------------

Should the HMS version be the version of the schema (from the HMS DB) or should it be the
version of the code they are running (like the fix you proposed) ? Ideally, they should be
the same but lets say given that HMS is standalone and can have its own release schedule and
that the schema version is not tied to the release version anymore, then they could differ.


> 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