[
https://issues.apache.org/jira/browse/PHOENIX-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samarth Jain updated PHOENIX-4203:
----------------------------------
Description: Currently, there is a guide post cache for every instance of
ConnectionQueryServicesImpl. If a user has multiple connection profiles, then
we will end up having one instance of guide post cache per such profile. This
is a bit wasteful since guide post cache is meant to be shared across the
Phoenix JDBC driver. (was: Currently, there is a guide post cache for every
instance of ConnectionQueryServicesImpl. If a user has multiple connection
profiles, then we will end up having one instance of guide post cache per such
profile. This is not optimal since guide post cache is meant to be shared
across the Phoenix JDBC driver.)
> GuidePost cache should be a singleton
> -------------------------------------
>
> Key: PHOENIX-4203
> URL: https://issues.apache.org/jira/browse/PHOENIX-4203
> Project: Phoenix
> Issue Type: Bug
> Reporter: Samarth Jain
>
> Currently, there is a guide post cache for every instance of
> ConnectionQueryServicesImpl. If a user has multiple connection profiles, then
> we will end up having one instance of guide post cache per such profile. This
> is a bit wasteful since guide post cache is meant to be shared across the
> Phoenix JDBC driver.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
