You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2021/12/07 08:42:00 UTC

[jira] [Assigned] (HBASE-26409) `MAXIMUN_KEY_LENGTH` changed from 0.20.0 to 0.20.2

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

Viraj Jasani reassigned HBASE-26409:
------------------------------------

    Assignee: thrylokya

> `MAXIMUN_KEY_LENGTH` changed from 0.20.0 to 0.20.2
> --------------------------------------------------
>
>                 Key: HBASE-26409
>                 URL: https://issues.apache.org/jira/browse/HBASE-26409
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.20.0, 0.20.2
>            Reporter: Yongkang Li
>            Assignee: thrylokya
>            Priority: Minor
>
> In HFile.java, there is a constant called `MAXIMUM_KEY_LENGTH`, which is used to check the validity of the key. However, the value changed from 64 * 1024 to Integer.MAX_VALUE. Therefore, I wonder whether it might throw an exception when checking the key after downgrading from 0.20.2 to 0.20.0.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)