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

   ### Describe the issue this Pull Request addresses
   
   This PR adds a configuration flag `hoodie.log.file.append.disabled` that 
allows users to disable appending to existing log files. When enabled, all 
appends go to a new log file instead of appending to an existing one.
   
   Issue: [HUDI-2350](https://issues.apache.org/jira/browse/HUDI-2350)
   
   ### Summary and Changelog
   
   **Summary:** Adds a new configuration option to control log file append 
behavior, useful for environments where appending to existing files is 
problematic.
   
   **Changelog:**
   - Added `LOG_FILE_APPEND_DISABLED` config property to `HoodieWriteConfig` 
with default value `false`
   - Added `withAppendDisabled(boolean)` method to 
`HoodieLogFormat.WriterBuilder`
   - Modified log file version computation to increment version when appends 
are disabled
   - Updated `TimelineArchiverV1` to use the new append disabled flag from 
config
   - Added unit test `testAppendDisabledFlag` in `TestHoodieLogFormat`
   
   ### Impact
   
   New configuration option for users who need to disable log file appending. 
No breaking changes - default behavior remains unchanged (appends enabled).
   
   ### Risk Level
   
   low - This is an additive change with a safe default value (disabled by 
default). Existing behavior is preserved unless explicitly opted into.
   
   ### Documentation Update
   
   The config description is included in the code. The new config is:
   - `hoodie.log.file.append.disabled` (default: `false`) - When enabled, all 
appends go to a new log file.
   
   ### 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