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

   ### Describe the issue this Pull Request addresses
   
   This PR refreshes the parquet-tools based clustering strategy from the older 
`parquet-tools` branch so it can be proposed against current `apache/master`.
   
   The original implementation had drifted from current Hudi internals and test 
APIs. This refresh keeps the existing simple rewrite hook shape while aligning 
the implementation with current clustering and storage behavior.
   
   ### Summary and Changelog
   
   Refresh the parquet-tools clustering strategy and its supporting tests for 
current master.
   
   - keep the `ParquetToolsExecutionStrategy` API simple with the existing 
file-to-file rewrite hook
   - generate a new output file id for clustering rewrites instead of reusing 
the source file id
   - migrate helper code to current `StoragePath` / `HoodieStorage` based APIs
   - replace brittle previous-commit extraction with 
`FSUtils.getCommitTime(...)`
   - update write-status generation to use current parquet/storage utilities
   - refresh the related tests to match current writer, meta client, and 
clustering strategy APIs
   
   ### Impact
   
   No public API change intended.
   
   This keeps the existing parquet-tools rewrite extension point, but makes it 
compatible with current Hudi master and current clustering output semantics.
   
   ### Risk Level
   
   low
   The change is localized to the parquet-tools rewrite path and related test 
scaffolding.
   
   ### Documentation Update
   
   none
   
   ### Contributor's checklist
   
   - [x] 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
   


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