You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2018/08/01 06:22:41 UTC
[jira] [Issue Comment Deleted] (HBASE-19508) ReadOnlyConfiguration
throws exception if any Configuration in current context calls
addDefautlResource
[ https://issues.apache.org/jira/browse/HBASE-19508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin updated HBASE-19508:
--------------------------
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> ReadOnlyConfiguration throws exception if any Configuration in current context calls addDefautlResource
> -------------------------------------------------------------------------------------------------------
>
> Key: HBASE-19508
> URL: https://issues.apache.org/jira/browse/HBASE-19508
> Project: HBase
> Issue Type: Bug
> Components: conf
> Reporter: stack
> Assignee: stack
> Priority: Major
> Fix For: 2.0.0-beta-1, 2.0.0
>
> Attachments: HBASE-19508.master.001.patch
>
>
> Reported by [~psomogyi] up on HBASE-19295, the issue that added CpEnv returning a read-only Configuration.
> Issue is that hadoop Configuration registers every created Configuration in a static REGISTRY on construction. A call to addDefaultResource -- e.g. sqoop does this in tests to get its configurations into the mix -- results in a call to every registered Configurations loadResource.. which is disallowed in our read-only Configuration.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)