[
https://issues.apache.org/jira/browse/HBASE-8372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13638705#comment-13638705
]
Jonathan Hsieh commented on HBASE-8372:
---------------------------------------
bq. When mutableConf is not null, can we get rid of the list of
ImmutableConfigMap's ?
bq. This consolidation can be achieved upon the first call to set().
[[email protected]], I don't that is correct unless we go through and copy all
the values from the parents. Doing that seems to negate the purpose of having
the CompoundConfiguariton. We also would lose the ability to change a parent
configuration under this config and have the change visible to
CompoundConfiguration (I believe there the original comments have something
about this).
> Provide mutability to CompoundConfiguration
> -------------------------------------------
>
> Key: HBASE-8372
> URL: https://issues.apache.org/jira/browse/HBASE-8372
> Project: HBase
> Issue Type: New Feature
> Reporter: Ted Yu
> Assignee: Jonathan Hsieh
> Attachments: hbase-8372.patch
>
>
> In discussion of HBASE-8347, it was proposed that CompoundConfiguration
> should support mutability.
> This can be done by consolidating ImmutableConfigMap's on first modification
> to CompoundConfiguration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
