[
https://issues.apache.org/jira/browse/HCATALOG-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arup Malakar updated HCATALOG-370:
----------------------------------
Attachment: J370-patch5.diff
Change summary:
1. use HCAT prefix
2. made the cache class package private after moving it to common
3. Only one cache instance and it uses unique thread id as one of the elements
in the cache key
4. Shutdown moved to a new method
5. Brought back threadsafety
6. Removed the configuration to disable the cache
7. Test case for multithreaded access and closeClients
> 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.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
