hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Demai Ni (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10941) default for max version isn't updated in doc after change on 0.96
Date Wed, 09 Apr 2014 03:38:18 GMT

    [ https://issues.apache.org/jira/browse/HBASE-10941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13963761#comment-13963761
] 

Demai Ni commented on HBASE-10941:
----------------------------------

[~tedyu], 

thanks. I probably didn't ask my question clear. the 'setMaxVersion' will only work for a
particular columfamily? and get invoked in ways, such like : >create 't1',{NAME=>'cf1',VERSIONS=>3}


I am wondering whether there is a way to change the setting globally. so that
{code}
>create 't1','cf1'
{code}
will get the old behavior with maxVersion as 3? 

my customers may get use of the old 'luxury' behavior, and raise such question. probably I
should just worry about it later. :-)  

> default for max version isn't updated in doc after change on 0.96
> -----------------------------------------------------------------
>
>                 Key: HBASE-10941
>                 URL: https://issues.apache.org/jira/browse/HBASE-10941
>             Project: HBase
>          Issue Type: Bug
>          Components: documentation
>            Reporter: Demai Ni
>            Assignee: Demai Ni
>            Priority: Minor
>              Labels: documentation
>             Fix For: 0.99.0
>
>         Attachments: HBASE-10941.patch
>
>
> HColumnDescriptor.DEFAULT_VERSIONS  change to 1 from 3 since 0.96. But webpage http://hbase.apache.org/book/schema.versions.html
hasn't reflected it yet. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message