flaneur2020 opened a new pull request, #7154:
URL: https://github.com/apache/opendal/pull/7154
# Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements. You can link an issue to this PR using the GitHub syntax. For
example `Closes #123` indicates that this PR will close issue #123.
-->
Closes #.
# Rationale for this change
<!--
Why are you proposing this change? If this is already explained clearly in
the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand your
changes and offer better suggestions for fixes.
-->
A planned upcoming change is to provide chunked cache capabilities for the
foyer layer, allowing large objects to be split into chunks for cached reads.
Before implementing this, I think it might be good to perform a simple
refactoring of the modules. This will help reduce the PR footprint when
introducing chunked cache later, ideally limiting the new logic to a single
additional file.
This PR has zero logic changes, it's just moving code around.
# What changes are included in this PR?
<!--
There is no need to duplicate the description in the issue here but it is
sometimes worth providing a summary of the individual changes in this PR.
-->
This PR sperates the single lib.rs into the following structure:
```
core/layers/foyer/src/
├── lib.rs
├── error.rs
├── full.rs
├── writer.rs
└── deleter.rs
```
# Are there any user-facing changes?
no
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
<!---
If there are any breaking changes to public APIs, please add the
`breaking-changes` label.
-->
# AI Usage Statement
<!--
If you are using AI tools to build this PR, please include a statement
specifying the tool and models you are using.
-->
I used Opus4.5 to make this refactor, and reviewed by myself.
--
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]
