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

Vihang Karajgaonkar commented on HIVE-21128:
--------------------------------------------

Looks like metastore tests on branch-3 are broken since the module name is 
pointing to standalone-metastore/metastore-server but metastore-server module 
doesn't exist on branch-3

2019-01-29 00:32:17,765  INFO [HostExecutor 3] 
HostExecutor.executeTestBatch:262 Drone [user=hiveptest, host=104.198.216.224, 
instance=0] executing UnitTestBatch 
[name=228_UTBatch_standalone-metastore__metastore-server_20_tests, id=228, 
moduleName=standalone-metastore/metastore-server, batchSize=20, 
isParallel=true, testList=[TestPartitionManagement, 
TestCatalogNonDefaultClient, TestCatalogOldClient, TestHiveAlterHandler, 
TestTxnHandlerNegative, TestTxnUtils, TestFilterHooks, TestRawStoreProxy, 
TestLockRequestBuilder, TestHiveMetastoreCli, TestCheckConstraint, 
TestAddPartitions, TestListPartitions, TestFunctions, TestGetTableMeta, 
TestTablesCreateDropAlterTruncate, TestRuntimeStats, TestDropPartitions, 
TestTablesList, TestUniqueConstraint]] with bash 
/home/hiveptest/104.198.216.224-hiveptest-0/scratch/hiveptest-228_UTBatch_standalone-metastore__metastore-server_20_tests.sh

> hive.version.shortname should be 3.2 on branch-3
> ------------------------------------------------
>
>                 Key: HIVE-21128
>                 URL: https://issues.apache.org/jira/browse/HIVE-21128
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Vihang Karajgaonkar
>            Assignee: Vihang Karajgaonkar
>            Priority: Major
>         Attachments: HIVE-21128.01.branch-3.patch, 
> HIVE-21128.02.branch-3.patch, HIVE-21128.03.branch-3.patch
>
>
> Since 3.1.0 is already release, the {{hive.version.shortname}} property in 
> the pom.xml of standalone-metastore should be 3.2.0. This version shortname 
> is used to generate the metastore schema version and used by Schematool to 
> initialize the schema using the correct script. Currently it using 3.1.0 
> schema init script instead of 3.2.0 init script



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

Reply via email to