Gabriel39 opened a new pull request, #68808:
URL: https://github.com/apache/doris/pull/68808

   ### What problem does this PR solve?
   
   Issue Number: N/A
   
   Related PR: N/A
   
   The large-string-map Parquet regression fixture contains two 1 GiB string 
keys in a column chunk larger than 2 GiB, with dictionary and PLAIN data pages. 
Materializing both rows into one output column requires a 4 GiB character 
buffer and can exceed the BE process memory limit during ASAN regression runs.
   
   Read this query with `batch_size=1` and disable aggregate pushdown using a 
statement-local hint. Both rows still go through full Map and string decoding, 
while each output batch contains only one large key. The query and its expected 
result remain unchanged. This retains the oversized Parquet column-chunk and 
mixed-encoding coverage; it no longer exercises accumulating both keys in one 
output ColumnString.
   
   ### Release note
   
   None
   
   ### Check List (For Author)
   
   - Test
       - [ ] Regression test
       - [ ] Unit Test
       - [x] Manual test
           - Compiled the modified suite with Groovy 4.0.19 successfully.
           - `git diff --check` passed.
           - Reviewed the batch-size validation and propagation to the native 
Parquet reader on branch-4.1.
           - The HDFS regression was not run locally: the original CI HDFS 
fixture environment is not configured. ASAN end-to-end validation remains for 
CI.
   - Behavior changed:
       - [x] No. Production code is unchanged; the existing test uses 
statement-local execution settings.
       - [ ] Yes.
   - Does this need documentation?
       - [x] No.
       - [ ] Yes.
   
   ### Check List (For Reviewer who merge this PR)
   
   - [ ] Confirm the release note
   - [ ] Confirm test cases
   - [ ] Confirm document
   - [ ] Add branch pick label
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to