refactor(file): introduce pluggable file store runtime - #8217
Open
LegendPei wants to merge 3 commits into
Open
Conversation
LegendPei
marked this pull request as ready for review
September 5, 2026 09:17
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ⅰ. Describe what this PR did
This PR introduces a pluggable runtime abstraction for Seata FileMode storage while preserving the existing file-based implementation as the default provider.
The main changes are:
FileStoreProviderandFileStoreRuntimeabstractions for FileMode storage.FileStoreProviderFactoryto select the provider throughstore.file.engine.DefaultFileStoreProvider.FileLockStoreand makeFileLockManagerdelegate lock operations to the selected store implementation.SessionHoldermanage the complete FileMode runtime lifecycle:LockerManagerFactorysupport typed FileMode lock-manager installation and reject FileMode access before its runtime is ready.LockManagerand coordinator instances from session, transaction and Console backend components.store.file.engine=defaultas the default configuration so the original FileMode implementation remains available through the new abstraction.Ⅱ. Does this pull request fix one issue?
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews