[MCOL-5429] GROUP_CONCAT execution allocates enourmous amount of RAM for its result RGDatas Created: 2023-02-20  Updated: 2023-05-12  Resolved: 2023-05-01

Status: Closed
Project: MariaDB ColumnStore
Component/s: ExeMgr, PrimProc
Affects Version/s: 22.08.7
Fix Version/s: 23.02.3

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

Issue Links:
Relates
relates to MCOL-5385 GROUP_CONCAT execution doesn't count ... Closed
Sprint: 2023-4, 2023-5, 2023-6
Assigned for Review: Roman Roman
Assigned for Testing: Daniel Lee Daniel Lee (Inactive)

 Description   

There is MDB client variable group_concat_max_len that controls the max length of GROUP_CONCAT output field. The variable default value differs by distros and can be either 1MB or 3 MB.
The value of this field sets the outcome RG column width here in buildAggregateColumn().
There are multiple places where code makes a new RowGroup and the corresponding RGData using 3MB as its column width and if a user sets the value to a higher value this causes PP to crash.
The suggested solution is to convert GROUP_CONCAT into a StringStore only column and avoid using group_concat_max_len value as a column width.



 Comments   
Comment by Gagan Goel (Inactive) [ 2023-05-01 ]

Fix for this issue is tested in the related ticket MCOL-5385. Marking this ticket as fixed.

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