You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Josh Elser (Jira)" <ji...@apache.org> on 2019/09/25 14:42:00 UTC
[jira] [Resolved] (PHOENIX-5489) Expected length of at least 8
bytes, but had 7 (state=22000,code=201)
[ https://issues.apache.org/jira/browse/PHOENIX-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Elser resolved PHOENIX-5489.
---------------------------------
Resolution: Invalid
Jira is a bug-tracker for changes made to the Phoenix code, not a support system for you to ask for help. Send an email to user@phoenix instead.
> Expected length of at least 8 bytes, but had 7 (state=22000,code=201)
> ---------------------------------------------------------------------
>
> Key: PHOENIX-5489
> URL: https://issues.apache.org/jira/browse/PHOENIX-5489
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.14.1
> Reporter: Ashish
> Priority: Major
> Fix For: 4.14.1
>
>
> As part of the process to upgrade phoenix from 4.7 to 4.14. We need to export all tables' data out. We found the following error during export one of the table. This indicates some data is not written to hbase by using phoenix client api or the one of the column data type has been changed. We got below error. I am not sure how to fix this. Need your assistance on this ASAP.
>
> java.sql.SQLException: ERROR 201 (22000): Illegal data. Expected length of at least 8 bytes, but had 7
> at org.apache.phoenix.mapreduce.PhoenixRecordReader.nextKeyValue(PhoenixRecordReader.java:159)
>
> This can be reproduced by running:
> select messageid from TABLE limit 100;
--
This message was sent by Atlassian Jira
(v8.3.4#803005)