[
https://issues.apache.org/jira/browse/HIVE-21484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16804172#comment-16804172
]
Vihang Karajgaonkar commented on HIVE-21484:
--------------------------------------------
The above test failure is a known flaky test failure as reported in HIVE-21396.
I have submitted a patch for HIVE-21396 to disable this test until we fix it.
While that gets reviewed and subimitted, I think its okay to go ahead and
commit this patch since there is no guarantee that {{vector_groupby_reduce}}
will not fail with v3 patch attached above.
> 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, HIVE-21484.02.patch,
> HIVE-21484.03.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)
