[jira] [Commented] (HIVE-16908) Failures in TestHcatClient due to HIVE-16844

["Sunitha Beeram (JIRA)" <ji...@apache.org>]

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

Sunitha Beeram commented on HIVE-16908:
---------------------------------------

[~mithun] sorry about being so anal about this, but with 2 metastores running in the same JVM we are always vulnerable to tests passing or failing due to weird reasons. I don't think fixing static-state is as much a priority (as we don't really have a use case to support running multiple metastores in the same JVM) - so if you think the tests have to use 2 metastores, then lets launch them in a way they would be launched? 

I am looking into the option of launching metastore in a different process.

> Failures in TestHcatClient due to HIVE-16844
> --------------------------------------------
>
>                 Key: HIVE-16908
>                 URL: https://issues.apache.org/jira/browse/HIVE-16908
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sunitha Beeram
>            Assignee: Sunitha Beeram
>         Attachments: HIVE-16908.1.patch, HIVE-16908.2.patch, HIVE-16908.3.patch
>
>
> Some of the tests in TestHCatClient.java, for ex:
> {noformat}
> org.apache.hive.hcatalog.api.TestHCatClient.testPartitionRegistrationWithCustomSchema (batchId=177)
> org.apache.hive.hcatalog.api.TestHCatClient.testPartitionSpecRegistrationWithCustomSchema (batchId=177)
> org.apache.hive.hcatalog.api.TestHCatClient.testTableSchemaPropagation (batchId=177)
> {noformat}
> are failing due to HIVE-16844. HIVE-16844 fixes a connection leak when a new configuration object is set on the ObjectStore. TestHCatClient fires up a second instance of metastore thread with a different conf object that results in the PersistenceMangaerFactory closure and hence tests fail. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)