voonhous opened a new pull request, #17880: URL: https://github.com/apache/hudi/pull/17880
### Describe the issue this Pull Request addresses This PR refactors the `hudi-common` module to reduce boilerplate code by leveraging Project Lombok annotations. Specifically, it replaces explicit `Logger` instantiation, manual getter/setter methods, and empty constructors with their equivalent Lombok annotations (`@Slf4j`, `@Getter`, `@Setter`,`@NoArgsConstructor`, `@AllArgsConstructor`, `@Data`, `@Value`, `@ToString`). This improves code readability and maintainability without altering the runtime logic. To make the PR more manageable, adding Lombok to `hudi-common` will be split into multiple parts. The scope here mainly covers / **INCLUDES** changes in: 1. `hudi-common/src/main/java/org/apache/hudi/common/bootstrap/index/hfile/` 2. `hudi-common/src/main/java/org/apache/hudi/common/model/` 3. `hudi-common/src/main/java/org/apache/hudi/common/table/` The changes here **EXCLUDES**: 1. `hudi-common/src/main/java/org/apache/hudi/common/model/BaseFile.java` 2. `hudi-common/src/main/java/org/apache/hudi/common/model/HoodieBaseFile.java` ### Summary and Changelog This change introduces the Lombok dependency to the `hudi-common` module and refactors several classes to utilize Lombok annotations. - Added lombok annotations wherever possible to `hudi-common` module. ### Impact - **Public API:** None. - **User Experience:** No visible change for end-users. - **Performance:** No impact (compile-time code generation). - **Code Health:** Reduces lines of code and standardizes logging/accessor patterns. ### Risk Level none (This is a pure refactoring change involving standard library annotations; no business logic was modified.) ### 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]
