[jira] [Closed] (PHOENIX-5455) IndexedKeyValue creation fails after HBASE-22034

["Chinmay Kulkarni (Jira)" <ji...@apache.org>]

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

Chinmay Kulkarni closed PHOENIX-5455.
-------------------------------------

Bulk closing Jiras for the 4.15.0 release.

> IndexedKeyValue creation fails after HBASE-22034
> ------------------------------------------------
>
>                 Key: PHOENIX-5455
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5455
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.15.0, 4.14.3
>            Reporter: Geoffrey Jacoby
>            Assignee: Geoffrey Jacoby
>            Priority: Blocker
>             Fix For: 4.15.0, 5.1.0
>
>         Attachments: PHOENIX-5455-4.14-HBase-1.5.patch, PHOENIX-5455-4.x-HBase-1.5.patch, PHOENIX-5455.4.x-HBase-1.5.v1.patch, PHOENIX-5455.patch
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> 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.4#803005)