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

Vihang Karajgaonkar commented on HIVE-16771:
--------------------------------------------

Test failures are unrelated and have been failing for other builds as well. I 
the one below are failing in 
https://builds.apache.org/job/PreCommit-HIVE-Build/5483 as well.

org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query23]
org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query14]
org.apache.hadoop.hive.cli.TestBeeLineDriver.testCliDriver[create_merge_compressed]
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[subquery_scalar]

Create HIVE-16796 for TestBeeLineDriver failure which has been failing 
consistently.

Below are known failures.
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[subquery_scalar]
 (batchId=152)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[vector_if_expr]
 (batchId=145)

TestTextFileHCatStorer.testWriteSmallint is failing with a disk error. 

> Schematool should use MetastoreSchemaInfo to get the metastore schema version 
> from database
> -------------------------------------------------------------------------------------------
>
>                 Key: HIVE-16771
>                 URL: https://issues.apache.org/jira/browse/HIVE-16771
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Vihang Karajgaonkar
>            Assignee: Vihang Karajgaonkar
>            Priority: Minor
>         Attachments: HIVE-16771.01.patch, HIVE-16771.02.patch, 
> HIVE-16771.03.patch, HIVE-16771.04.patch
>
>
> HIVE-16723 gives the ability to have a custom MetastoreSchemaInfo 
> implementation to manage schema upgrades and initialization if needed. In 
> order to make HiveSchemaTool completely agnostic it should depend on 
> IMetastoreSchemaInfo implementation which is configured to get the metastore 
> schema version information from the database. It should also not assume the 
> scripts directory and hardcode it itself. It would rather ask 
> MetastoreSchemaInfo class to get the metastore scripts directory.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to