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

   ### Change Logs
   
   - Fix issue in HoodieTestDataGenerator where multiple updates were created 
for the same key
   - Update `TestHoodieFileGroupReaderBase` to handle the comparison logic and 
to use the generated records as the expected values instead of re-reading the 
values. In the future, there will not be a non-FGReader path so we need to 
anticipate that.
   - Add placeholders for setting up tests where `populateMetaFields` is set to 
false
   
   ### Impact
   
   Splits out the refactoring of our tests into its own PR to cut down on the 
size of the code changes. This also adds data validations to tests whereas 
previous counts were being used and only a single file slice was being queried.
   
   ### Risk level (write none, low medium or high below)
   
   None, this is strictly test improvements
   
   ### 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