You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Samarth Jain (JIRA)" <ji...@apache.org> on 2016/01/16 00:22:39 UTC
[jira] [Resolved] (PHOENIX-2119) Do not copy underlying HBase
configuration properties when connection properties are supplied
[ https://issues.apache.org/jira/browse/PHOENIX-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Samarth Jain resolved PHOENIX-2119.
-----------------------------------
Resolution: Fixed
> Do not copy underlying HBase configuration properties when connection properties are supplied
> ---------------------------------------------------------------------------------------------
>
> Key: PHOENIX-2119
> URL: https://issues.apache.org/jira/browse/PHOENIX-2119
> Project: Phoenix
> Issue Type: Improvement
> Reporter: James Taylor
> Assignee: Samarth Jain
> Labels: ReadOnlyDB, SFDC
> Fix For: 4.7.0
>
> Attachments: PHOENIX-2119.patch, PHOENIX-2119_v2.patch
>
>
> Related to PHOENIX-1958, we can avoid copying the underlying HBase configuration properties when connection properties are supplied by keeping an override maps on ConnectionQueryServices. In this case, a ReadOnlyProperty get will be first done on the override map and then subsequently on the base/shared map for the HBase configuration properties.
> The reason to do this is because some applications always provide connection properties (usually for custom annotations that identify the tenant and request) and the memory overhead of copying *all* properties is too high.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)