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

   ### Describe the issue this Pull Request addresses
   
   Closes #19465.
   
   `HoodieTableState` retained eight fields after the FileGroupReader 
migration, but `HoodieMergeOnReadRDDV2` only read `latestCommitTimestamp`. 
Because the case class was an RDD constructor field, every MOR task serialized 
the remaining table path, merge configuration, and metadata configuration 
without consuming them.
   
   ### Summary and Changelog
   
   - Remove `HoodieTableState` and its construction from `HoodieBaseRelation`.
   - Retain the query's latest commit timestamp directly on the relation.
   - Pass only that `Option[String]` to `HoodieMergeOnReadRDDV2` from the 
snapshot and incremental relation variants.
   
   ### Impact
   
   No public API or behavior change. The MOR read path serializes only the 
timestamp it uses instead of an otherwise write-only table-state object.
   
   ### Risk Level
   
   Low. This is a mechanical narrowing of an internal constructor parameter. 
All references to `HoodieTableState`, the old named argument, and its field 
access were removed. `git diff --check` passes.
   
   The local environment does not contain Java or Maven, so the Scala module 
could not be compiled locally; hosted CI is required for compilation and test 
coverage.
   
   ### Documentation Update
   
   None; this is an internal implementation cleanup with no user-facing change.
   
   ### Contributor's checklist
   
   - [ ] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [x] Enough context is provided in the sections above
   - [x] Adequate tests were added if applicable (no behavior change; existing 
MOR coverage exercises the constructor paths)
   
   Developed with assistance from OpenAI Codex.
   


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