[
https://issues.apache.org/jira/browse/HIVE-16908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16111334#comment-16111334
]
Mithun Radhakrishnan commented on HIVE-16908:
---------------------------------------------
bq. I am looking into the option of launching metastore in a different process.
Thank you for holding out for the proper solution to this, [~sbeeram]. A couple
of challenges come to mind:
# The test will need to communicate which port the remote metastore was started
at. We might consider pre-setting the port, but I wonder if this might make the
test's start-up brittle.
# Cleanup for the remote metastore's state, after the test.
bq. sorry about being so anal about this...
I fear that label fits my stand more than yours. :/
In the spirit of detente, I'd be happy to revisit your first proposal, if the
multi-process solution proves cumbersome.
> 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)
