[
https://issues.apache.org/jira/browse/HIVE-16908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075593#comment-16075593
]
Mithun Radhakrishnan commented on HIVE-16908:
---------------------------------------------
Yes, this is what I was afraid of. The intention of
{{testTableSchemaPropagation()}} was to simulate table-propagation across
different clusters/HCat instances, as Apache Falcon (or similar projects) do. I
wonder if this change dilutes that intention. :/ I do recognize that the static
state in {{ObjectStore}} makes this problematic. I'm trying to figure out an
alternative.
Question: If the target metastore instance were accessed through a different
classloader, their states would be isolated, right? Would that be an acceptable
solution?
> 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
>
>
> 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)
