[MCOL-4519] Certain functions in projection and filtering fails in ColumnCommand::projectResultRG() with primMsg->NVALS != outMsg->NVALS Created: 2021-01-28  Updated: 2021-02-05  Resolved: 2021-02-04

Status: Closed
Project: MariaDB ColumnStore
Component/s: PrimProc
Affects Version/s: 6.1.1
Fix Version/s: 6.1.1

Type: Bug Priority: Major
Reporter: Roman Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MCOL-4188 Verify the whole Full DECIMAL patch a... Closed
Sprint: 2021-2

 Description   

Consider the example:

create table t3 ( CIDX INTEGER, CSMALLINT SMALLINT  )engine=columnstore;
insert into t3 values (1,-43),(2,-45),(3,-46);
ALTER TABLE t3 ADD COLUMN CUSMALLINT SMALLINT UNSIGNED;
update t3 set cusmallint=csmallint+20000;
 
MariaDB [tpch1]> select LEAST(CUSMALLINT,CSMALLINT) from t3;
ERROR 1815 (HY000): Internal error: An unexpected condition within the query caused an internal processing error within Columnstore. Please check the log files for more details. Additional Information: error in BatchPrimitivePro
MariaDB [tpch1]> 

ColumnCommand::projectResultRG() detects that primMsg->NVALS != outMsg->NVALS and throws an exception.



 Comments   
Comment by Roman [ 2021-02-02 ]

4QA there are two patterns to test: the functions that takes an added int column as an argument, e.g. least and the join with an added column in the join predicate.

Comment by Daniel Lee (Inactive) [ 2021-02-04 ]

Build verified: 6.1.1 (Drone #1620)

Verified mentioned test case as well as self-join using added column.

Generated at Thu Feb 08 02:50:58 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.