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

   ### Change Logs
   
   Adding write config to support streaming writes to metadata table. 
   Config is named "hoodie.write.streaming.writes.to.metadata". 
   
   This feature lies in the fast path and so adding a fallback option just 
incase we run into any issues after official release. In 2 releases once it 
deemed to be stable, we can remove the write config totally. 
   
   By default in SPARK engine we can enable it, and leave it disabled for FLINK 
and JAVA.
   
   This patch is just about adding the write config. its not wired anywhere. 
   We are going to raise lot of smaller patches as part of 
https://issues.apache.org/jira/browse/HUDI-9281. 
   for overall design, feel free to check out 
https://github.com/apache/hudi/pull/13236 
   
   ### Impact
   
   Nothing for now.
   
   ### Risk level (write none, low medium or high below)
   
   none. 
   
   ### 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 create a Jira ticket, attach the
     ticket number here and 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)
   - [ ] Change Logs and Impact were stated clearly
   - [ ] Adequate tests were added if applicable
   - [ ] CI passed
   


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