nsivabalan opened a new pull request, #17477:
URL: https://github.com/apache/hudi/pull/17477

   ### Describe the issue this Pull Request addresses
   
   We added streaming write support to metadata table in spark in release 
1.1.0. 
   Ref patch: https://github.com/apache/hudi/pull/13976. 
   
   Based on the spark runtime used (EMR, EKS,etc), the writes to data table may 
or may not happen with the intended stage. in EMR, it happens in the intended 
stage. but in EKS, writes to data table happens after [colaescing data table 
write status 
rdd](https://github.com/apache/hudi/blob/2741a2a8f2ba82b8bde5648ce71caa354e5f91b0/hudi-client/hudi-spark-client/src/main/java/org/apache/hudi/client/StreamingMetadataWriteHandler.java#L116)
 which could cause a huge performance hit. 
   
   ### Summary and Changelog
   
   - Fixing streaming writes to metadata table to ensure writes to data table 
happens in the intended stage irrespective of spark environment used. 
   
   ### Impact
   
   - Fixing regression caused in 1.1.0 writes using spark engine (non EMR 
environments). 
   
   ### Risk Level
   
   high. 
   
   ### Documentation Update
   
   <!-- Describe any necessary documentation update if there is any new 
feature, config, or user-facing change. If not, put "none".
   
   - The config description must be updated if new configs are added or the 
default value of the configs are changed.
   - Any new feature or user-facing change requires updating the Hudi website. 
Please follow the 
     [instruction](https://hudi.apache.org/contribute/developer-setup#website) 
to make changes to the website. -->
   
   ### Contributor's checklist
   
   - [ ] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [ ] Enough context is provided in the sections above
   - [ ] Adequate tests were added if applicable
   


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