[
https://issues.apache.org/jira/browse/HBASE-10950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973410#comment-13973410
]
Enoch Hsu commented on HBASE-10950:
-----------------------------------
isnt that what .getInt() does? my understanding is it attempts to retrieve the
config value (which in this case is from hbase-site.xml) and if there is none
will set it to 1. which was the original default value.
Or are you saying that places that call "HColumnDescriptor.getMaxVersions()"
should instead first do some sort of call to a config object to retrieve
hbase.column.max.version and if that is null then call
HColumnDescriptor.getMaxVersions?
I also am not quite sure what you mean by "people won't have a chance to add
customizations to their conf object". They can just add it to hbase-site.xml
and it will get parsed in won't it? At least that is the behavior I observed
when testing hbase shell
> Add a configuration point for MaxVersion of Column Family
> ----------------------------------------------------------
>
> Key: HBASE-10950
> URL: https://issues.apache.org/jira/browse/HBASE-10950
> Project: HBase
> Issue Type: Improvement
> Components: Admin
> Affects Versions: 0.98.0, 0.96.0
> Reporter: Demai Ni
> Assignee: Enoch Hsu
> Fix For: 0.99.0, 0.98.2, 0.96.3
>
> Attachments: HBASE_10950.patch, HBASE_10950_v2.patch
>
>
> Starting on 0.96.0. HColumnDescriptor.DEFAULT_VERSIONS change to 1 from 3.
> So a columnfamily will be default have 1 version of data. Currently a user
> can specifiy the maxVersion during create table time or alter the columnfam
> later. This feature will add a configuration point in hbase-sit.xml so that
> an admin can set the default globally.
> a small discussion in
> [HBASE-10941|https://issues.apache.org/jira/browse/HBASE-10941] lead to this
> jira
--
This message was sent by Atlassian JIRA
(v6.2#6252)
