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

   ### Change Logs
   
   - Adds MoR specific action executors to fix functionality in the java 
client. Specifically we were seeing that all inserts were resulting in base 
files even when using the in-memory index which should result in only log files 
being written
   - Updates a java client test to assert this functionality with in-memory 
index
   - Re-enable the test in `TestHoodieFileGroupReaderOnHive`
   
   ### Impact
   
   - Fixes functionality for the java client when the index supports indexing 
of log files, which is required for the FileGroupReader functional test suite
   
   ### Risk level (write none, low medium or high below)
   
   None, this follows the pattern used by the spark client and there are 
existing functional tests around the java client to ensure existing 
functionality does not break as a result
   
   ### 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