Laksh Singla 5f588fa45c Fix bug while materializing scan's result to frames (#15987) ... While converting Sequence<ScanResultValue> to Sequence<Frames>, when maxSubqueryBytes is enabled, we batch the results to prevent creating a single frame per ScanResultValue. Batching requires peeking into the actual value, and checking if the row signature of the scan result’s value matches that of the previous value. Since we can do this indefinitely (in the worst case all of them have the same signature), we keep fetching them and accumulating them in a list (on the heap). We don’t really know how much to batch before we actually write the value as frames. The PR modifies the batching logic to not accumulate the results in an intermediary list		2024-03-07 17:11:44 +05:30
..
src	Fix bug while materializing scan's result to frames (#15987)	2024-03-07 17:11:44 +05:30
pom.xml	Introduce dynamic table append (#15897)	2024-03-01 04:31:57 -05:00