the-other-tim-brown opened a new pull request, #13422:
URL: https://github.com/apache/hudi/pull/13422

   ### Change Logs
   
   While running table services asynchronously in the Streamer, we discovered 
the timeline server can only serve one write client at a time safely. When 
there are multiple write clients, the "last instant" sent to the service can 
change and cause the view to be updated. At this point, the first client's view 
of the table will have been updated mid process which can cause issues with 
generating a consistent view of the table.
   
   The Streamer also shares the same instance of the WriteClient between 
multiple threads. The class is not designed to be thread-safe so this can lead 
to further issues.
   
   This PR adds helper methods to generate a new client with the same config 
but will use a separate embedded timeline service (if enabled) to solve the 
above issues.
   
   ### Impact
   
   Ensures safe operations with async table services in the Streamer
   
   ### Risk level (write none, low medium or high below)
   
   Low
   
   ### 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