[MCOL-4643] UDAF may return bad value when it should return NULL Created: 2021-03-26  Updated: 2021-05-04  Resolved: 2021-05-04

Status: Closed
Project: MariaDB ColumnStore
Component/s: ExeMgr
Affects Version/s: 5.5.1
Fix Version/s: 5.6.1

Type: Bug Priority: Blocker
Reporter: David Hall (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Sprint: 2021-5, 2021-6, 2021-7

 Description   

During final evaluation of UDAF, if the result should be NULL and if, in that particular thread, a non-NULL value has already been created for another row (because of GROUP BY), that other calculated number is returned, rather than NULL.

This is because the variable used to store the result is not reset inside the loop.

During execution, this is unpredictable because one never knows which rows will be evaluated in which threads.



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

It is not merged into branch develop-5 for 5.6.1

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

Build verified: 5.6.1 ( Drone #2302 )

Verified by ColumnStore MTR regression test suite.

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