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

   ## What changed
   
   - Backport #61762 to add the TPC-H MOR unique-key regression suite, 
including MOR-versus-DUP comparison and MOR value-predicate-pushdown coverage.
   - Backport #62335 to rename the suite from SF10 to SF100, switch its S3 
paths and expected row counts to SF100, and add the 22 auto-discovered SQL 
expected-output files.
   
   ## Why
   
   #62335 depends on the suite introduced by #61762. `branch-4.1` does not 
contain #61762, so cherry-picking #62335 alone reports `rename/delete` 
conflicts for the entire suite because the rename source files are absent. 
Backporting #61762 first makes the dependency explicit and allows #62335 to 
apply cleanly as the intended directory rename.
   
   ## Impact
   
   This adds branch-4.1 regression coverage for reading Merge-on-Read 
unique-key tables as duplicate-key tables and for MOR value predicate pushdown 
at TPC-H SF100 scale. It changes regression tests only and does not modify 
product code.
   
   ## Validation
   
   - Cherry-picked #61762 and then #62335 with `-x`; both applied without 
conflicts in this order.
   - Verified the final `tpch_sf100_unique_mor_p2` suite and expected-output 
subtree are byte-for-byte identical to upstream #62335.
   - Verified all 22 expected-output files are identical to the existing 
`tpch_sf100_p2` outputs from which they were copied.
   - Verified `read_mor_as_dup_tables` and 
`enable_mor_value_predicate_pushdown_tables` already exist on `branch-4.1`.
   - Not run: the full SF100 regression suite, which requires the external 
SF100 dataset and performs two full loads into both MOR and DUP tables.
   
   The upstream change itself has end-of-file blank-line warnings in `q06.sql` 
and `q21.sql`; this backport preserves those files unchanged.
   


-- 
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