lucasfang opened a new pull request, #91:
URL: https://github.com/apache/paimon-cpp/pull/91

   ### Purpose
   
   Linked issue: No linked issue
   
   This change adds file store write and restore utilities for the paimon-cpp 
core operation module.
   
   Included changes:
   
   - **Public API** (`include/paimon/`):
     - Adds `write_context.h` defining write session context and configuration.
     - Adds `file_store_write.h` defining the file store write interface.
   
   - **Core Operation Implementation** (`src/paimon/core/operation/`):
     - Adds `abstract_file_store_write.h/.cpp` providing base implementation 
for file store writers.
     - Adds `file_store_write.cpp` implementing concrete file store write logic.
     - Adds `write_context.cpp` implementing write context management.
     - Adds `write_restore.h/.cpp` providing write restore capabilities.
     - Adds `file_system_write_restore.h` defining file-system-level restore 
interface.
     - Adds `restore_files.h` defining restore file metadata structures.
   
   - **Test Coverage**:
     - Adds `file_store_write_test.cpp` covering file store write functionality.
     - Adds `write_context_test.cpp` covering write context behavior.
     - Adds `file_system_write_restore_test.cpp` covering file system restore 
logic.
     - Adds `write_restore_test.cpp` covering write restore operations.
   
   ### Tests
   
   Not run. Local compile, CMake, and gtest environment checks are not part of 
this PR description.
   
   Test coverage included in this change:
   
   - `FileStoreWriteTest`
   - `WriteContextTest`
   - `FileSystemWriteRestoreTest`
   - `WriteRestoreTest`
   
   ### API and Format
   
   This change adds public API in `include/paimon/write_context.h` and 
`include/paimon/file_store_write.h`.
   
   No storage format or protocol changes.
   
   ### Documentation
   
   No documentation changes required.
   
   ### Generative AI tooling
   
   Migrate-by: Aone Copilot (Qwen-3.7-Max)
   


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