XiaoHongbo-Hope opened a new pull request, #9360:
URL: https://github.com/apache/paimon/pull/9360

   ## What changed
   
   - Materialize narrow matched update/delete rows before the file-routing 
shuffle in generic Ray MERGE.
   - Keep self-merge streaming and leave other row-id writers unchanged.
   
   ## Why
   
   When a lazy source already contains a join or shuffle, Ray can schedule the 
source join, MERGE target join, and file-routing shuffle in one streaming plan. 
On a 2-CPU cluster, shuffle aggregators can reserve the available resources and 
indefinitely starve the final routing stage.
   
   The new boundary separates the matched join from file routing without 
materializing the full source.
   
   ## Tests
   
   - Joined BLOB transform and matched update on 2 CPUs
   - Joined source and matched delete on 2 CPUs
   - Self-merge no-materialization regression
   - 127 Ray MERGE tests
   - 52 update/conflict/core commit tests
   - 24 table MERGE API tests
   - flake8, py_compile, and git diff check


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

Reply via email to