[
https://issues.apache.org/jira/browse/HIVE-15062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15610226#comment-15610226
]
Siddharth Seth commented on HIVE-15062:
---------------------------------------
[~sershe] - if you're referring to the following
{code}
org.apache.hadoop.hive.cli.TestHBaseCliDriver.testCliDriver[hbase_bulk]
(batchId=89)
{code}
There's already a flaky test jira for this under
https://issues.apache.org/jira/browse/HIVE-15058. (That's tracking currently
known flaky tests to make it a little easier to analyze ptest reports, cite
jiras, and commit). Of course if you have an idea on how this test can be
fixed, that would be awesome. (Looks like you know more than anyone else on
what is going on with the test :))
This specific failure, I think we should just disable, it fails often enough to
not be useful.
> create backward compat checking for metastore APIs
> --------------------------------------------------
>
> Key: HIVE-15062
> URL: https://issues.apache.org/jira/browse/HIVE-15062
> Project: Hive
> Issue Type: Bug
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: HIVE-15062.01.nogen.patch, HIVE-15062.01.patch,
> HIVE-15062.02.nogen.patch, HIVE-15062.02.patch, HIVE-15062.nogen.patch,
> HIVE-15062.patch
>
>
> This is to add client capability checking to Hive metastore.
> This could have been used, for example, when introducing ACID tables - a
> client trying to get_table on such a table without specifying that it is
> aware of ACID tables would get an error by default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
