You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Konstantin Ryakhovskiy (JIRA)" <ji...@apache.org> on 2016/06/27 13:47:52 UTC
[jira] [Commented] (HBASE-15583) Discuss mutable vs immutable
HTableDescriptor
[ https://issues.apache.org/jira/browse/HBASE-15583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351023#comment-15351023 ]
Konstantin Ryakhovskiy commented on HBASE-15583:
------------------------------------------------
They are used in the hbase-client, HTable.getTableDescriptor().
From my perspective, since it is a public API, then it makes sense to:
- first mark it as deprecated
- and create new method to return mutable (modifiable) HTableDescriptor.
> Discuss mutable vs immutable HTableDescriptor
> ---------------------------------------------
>
> 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
> 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.4#6332)