You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Geoffrey Jacoby (Jira)" <ji...@apache.org> on 2019/08/27 18:24:00 UTC

[jira] [Resolved] (HBASE-22934) IndexedKeyValue creation fails after HBASE-22034

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

Geoffrey Jacoby resolved HBASE-22934.
-------------------------------------
    Resolution: Invalid

> IndexedKeyValue creation fails after HBASE-22034
> ------------------------------------------------
>
>                 Key: HBASE-22934
>                 URL: https://issues.apache.org/jira/browse/HBASE-22934
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Geoffrey Jacoby
>            Assignee: Geoffrey Jacoby
>            Priority: Major
>
> HBASE-22034 backported to branch-1 HBASE-21401 (adding several validation checks to KeyValue creation) and HBASE-22032 (adding a null check for the row key to KeyValue creation). It will first be released in HBase 1.5.
> In Phoenix 4.14.2 we included PHOENIX-5188, which adds logic to initialize IndexedKeyValues with the appropriate row key and offsets, so that it can pass the new check in HBASE-22032. However, it did not correctly handle all the checks in HBASE-21401. 
> When testing 4.14.3 of Phoenix with an HBase version containing HBASE-22034, we see lots of errors like the following:
> java.lang.IllegalArgumentException: Overflow when reading key length at position=0, KeyValueBytesHex=foo, offset=0, length=3
> This will affect the future 4.15-HBase-1.5, and as well as any future release of a 4.14.3 based on HBase-1.5



--
This message was sent by Atlassian Jira
(v8.3.2#803003)