You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Chen Feng (Jira)" <ji...@apache.org> on 2020/12/03 11:09:00 UTC
[jira] [Created] (PHOENIX-6243) ValueBitSet can be "true" for
incorrect columns
Chen Feng created PHOENIX-6243:
----------------------------------
Summary: ValueBitSet can be "true" for incorrect columns
Key: PHOENIX-6243
URL: https://issues.apache.org/jira/browse/PHOENIX-6243
Project: Phoenix
Issue Type: Bug
Affects Versions: 4.15.0
Reporter: Chen Feng
Assignee: Chen Feng
ValueBitSet can be "true" for incorrect columns. Execute the following sqls
CREATE TABLE A(ID UNSIGNED_LONG NOT NULL PRIMARY KEY, COL_0 UNSIGNED_LONG, COL_1 UNSIGNED_LONG, COL_2 UNSIGNED_LONG, COL_3 UNSIGNED_LONG, COL_4 UNSIGNED_LONG, COL_5 UNSIGNED_LONG, COL_6 UNSIGNED_LONG, COL_7 UNSIGNED_LONG, COL_8 UNSIGNED_LONG, COL_9 UNSIGNED_LONG, COL_10 UNSIGNED_LONG, COL_11 UNSIGNED_LONG, COL_12 UNSIGNED_LONG, COL_13 UNSIGNED_LONG, COL_14 UNSIGNED_LONG)
CREATE TABLE B(ID UNSIGNED_LONG NOT NULL PRIMARY KEY, S_ VARCHAR, UL_ UNSIGNED_LONG)
UPSERT INTO A VALUES(1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1)
UPSERT INTO B(ID, UL_) VALUES(1, 1)
SELECT /*+ USE_SORT_MERGE_JOIN */ J_A.ID, J_A.COL_0, J_A.COL_1, J_A.COL_2, J_A.COL_3, J_A.COL_4, J_A.COL_5, J_A.COL_6, J_A.COL_7, J_A.COL_8, J_A.COL_9, J_A.COL_10, J_A.COL_11, J_A.COL_12, J_A.COL_13, J_A.COL_14, J_B.S_, J_B.UL_ FROM ( SELECT ID, COL_0, COL_1, COL_2, COL_3, COL_4, COL_5, COL_6, COL_7, COL_8, COL_9, COL_10, COL_11, COL_12, COL_13, COL_14 FROM A) J_A JOIN ( SELECT ID, S_, UL_ FROM B) J_B ON J_A.ID = J_B.ID
will trigger exception as follows
Error: ERROR 201 (22000): Illegal data. Expected length of at least 8 bytes, but had 7 (state=22000,code=201)
java.sql.SQLException: ERROR 201 (22000): Illegal data. Expected length of at least 8 bytes, but had 7
--
This message was sent by Atlassian Jira
(v8.3.4#803005)