[jira] [Commented] (PHOENIX-2119) Do not copy underlying HBase configuration properties when connection properties are supplied

["Hudson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PHOENIX-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15151123#comment-15151123 ] 

Hudson commented on PHOENIX-2119:
---------------------------------

FAILURE: Integrated in Phoenix-master #1142 (See [https://builds.apache.org/job/Phoenix-master/1142/])
PHOENIX-2119 Do not copy underlying HBase configuration properties when (jtaylor: rev 9e2b4339242588f36a71a3920b36b2e2c7867d2d)
* phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixConnection.java


> 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_addendum.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)