[
https://issues.apache.org/jira/browse/HCATALOG-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arup Malakar updated HCATALOG-370:
----------------------------------
Attachment: J370-patch6.diff
1. Casting the Exception back to what actually it is, while creating the
HiveMetaStoreClient. In the last implementation it was always getting wrapped
as IOExceptoin causing the test
org.apache.hcatalog.mapreduce.TestPassProperties.testSequenceTableWriteReadMR()
to fail.
2. Updated svn and resolved conflict in FileOutputCommitterContainer.java
Review: https://reviews.apache.org/r/6114/diff/7-8/#index_header
> Create a HiveMetaStoreClient cache in hcatalog
> ----------------------------------------------
>
> Key: HCATALOG-370
> URL: https://issues.apache.org/jira/browse/HCATALOG-370
> Project: HCatalog
> Issue Type: Improvement
> Components: client
> Affects Versions: 0.4
> Reporter: Rohini Palaniswamy
> Assignee: Arup Malakar
> Priority: Minor
> Attachments: J370-patch1.diff, J370-patch2.diff, J370-patch3.diff,
> J370-patch4.diff, J370-patch5.diff, J370-patch6.diff, J370.patch
>
>
> Hcat makes multiple calls to hivemetastore client and every time the
> connection is setup and destroyed which is costly. It would be nice to have a
> centralized cache, that has a connection per unique identifier (ugi,hcat
> server uri and anything else mandatory). Instead of creating clients all over
> the code, it can be retrieved from this cache. Connections in the cache can
> be closed using WeakReference and ReferenceQueue or based on some time
> interval.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
