hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amandeep Khurana (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-1895) HConstants.MAX_ROW_LENGTH is incorrectly 64k, should be 32k
Date Fri, 09 Oct 2009 19:47:31 GMT

     [ https://issues.apache.org/jira/browse/HBASE-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Amandeep Khurana updated HBASE-1895:
------------------------------------

    Assignee: Amandeep Khurana

> HConstants.MAX_ROW_LENGTH is incorrectly 64k, should be 32k
> -----------------------------------------------------------
>
>                 Key: HBASE-1895
>                 URL: https://issues.apache.org/jira/browse/HBASE-1895
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.20.0
>            Reporter: ryan rawson
>            Assignee: Amandeep Khurana
>             Fix For: 0.20.1, 0.21.0
>
>
> the max length of a row has to fit into a signed short. That is 32k.  The constant is
incorrect, but in the depths of KeyValue it does the right thing:
>     if (rlength > Short.MAX_VALUE) {
>       throw new IllegalArgumentException("Row > " + Short.MAX_VALUE);
>     }
> so your Put wont fail and instead it will fail in the KeyValue constructor.  So far only
that 1 line in Put uses this constant, but we should have a correct value here. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message