[IMPALA-12035] Impala accepts very big numbers but fails to store them correctly

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Impala 4.3.0
• Epic Color: ghx-label-11
• Assignee: Daniel Becker
• Reporter: Bakai Ádám
• Created: 31/Mar/23 10:32
• Updated: 25/Apr/24 19:56
• Resolved: 11/May/23 21:43

Description

I tried  to insert rows very big bigints, and it worked as expected with big integers (error message, no new row stored), but it didn’t work as expected with ridiculously big integers( no error message, stored incorrect value). Here are the commands used:

drop TABLE my_first_table2;

CREATE TABLE my_first_table2
(
  id BIGINT,
  name STRING,
  PRIMARY KEY(id)
);

INSERT INTO my_first_table2 VALUES (cast(9 as BIGINT), "sarah");
-- this works just fine as expected


INSERT INTO my_first_table2 VALUES (cast(9999999999999999999999 as BIGINT), "sarah");
-- ERROR: UDF ERROR: Decimal expression overflowed which is expected since it is over bigint max value (source: https://impala.apache.org/docs/build/plain-html/topics/impala_bigint.html#:~:text=Range%3A%20%2D9223372036854775808%20..,9223372036854775807. )

INSERT INTO my_first_table2 VALUES (cast(999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999 as BIGINT), "sarah");
-- this succeeds and doesn't throw the same error as the previous command which is concerning

select * from my_first_table2;
-- there are two rows in the table, and the id is incorrect in one of them  

Issue Links

• relates to: IMPALA-12950 Improve error message in case of out-of-range numeric conversions