Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
22.08.7
-
None
-
2023-4, 2023-5, 2023-6
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.
Attachments
Issue Links
- relates to
-
MCOL-5385 GROUP_CONCAT execution doesn't count RAM used to store data properly crashing PrimProc runtime
-
- Closed
-
Activity
Fix Version/s | 23.02 [ 28209 ] |
Sprint | 10.4.0-1 [ 254 ] | 2022-24 [ 698 ] |
Rank | Ranked higher |
Sprint | 2023-4 [ 698 ] | 2023-4, 2023-5 [ 698, 702 ] |
Sprint | 2023-4, 2023-5 [ 698, 702 ] | 2023-4, 2023-5, 2023-6 [ 698, 702, 706 ] |
Assignee | Leonid Fedorov [ JIRAUSER48443 ] | Gagan Goel [ tntnatbry ] |
Status | Open [ 1 ] | Confirmed [ 10101 ] |
Status | Confirmed [ 10101 ] | In Progress [ 3 ] |
Assigned for Review | Roman [ drrtuy ] | |
Assigned for Testing | Daniel Lee [ dleeyh ] |
Fix Version/s | 23.02.3 [ 28901 ] | |
Fix Version/s | 23.02 [ 28209 ] |
Status | In Progress [ 3 ] | In Review [ 10002 ] |
Status | In Review [ 10002 ] | In Testing [ 10301 ] |
Resolution | Fixed [ 1 ] | |
Status | In Testing [ 10301 ] | Closed [ 6 ] |
Fix for this issue is tested in the related ticket
MCOL-5385. Marking this ticket as fixed.