You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Chia-Ping Tsai (JIRA)" <ji...@apache.org> on 2017/03/22 16:51:41 UTC
[jira] [Updated] (HBASE-15583) Any HTD we give out should be
immutable
[ https://issues.apache.org/jira/browse/HBASE-15583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chia-Ping Tsai updated HBASE-15583:
-----------------------------------
Summary: Any HTD we give out should be immutable (was: Discuss mutable vs immutable HTableDescriptor)
> Any HTD we give out should be immutable
> ---------------------------------------
>
> Key: HBASE-15583
> URL: https://issues.apache.org/jira/browse/HBASE-15583
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 2.0.0
> Reporter: Gabor Liptak
> Assignee: Chia-Ping Tsai
> Priority: Minor
> Labels: beginner
> Fix For: 2.0.0
>
>
> From [~enis] in https://issues.apache.org/jira/browse/HBASE-15505:
> PS Should UnmodifyableHTableDescriptor be renamed to UnmodifiableHTableDescriptor?
> It should be named ImmutableHTableDescriptor to be consistent with collections naming. Let's do this as a subtask of the parent jira, not here. Thinking about it though, why would we return an Immutable HTD in HTable.getTableDescriptor() versus a mutable HTD in Admin.getTableDescriptor(). It does not make sense. Should we just get rid of the Immutable ones?
> We also have UnmodifyableHRegionInfo which is not used at the moment it seems.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)