-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove the temporary caching feature flag #622
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small note on changelog.
Code changes LGTM.
mountpoint-s3/CHANGELOG.md
Outdated
* No breaking changes. | ||
|
||
### Other changes | ||
* Introduced the `--cache` option to configure Mountpoint to cache object metadata and content, in order to reduce cost and improve performance for repeated reads to the same files. ([#622](https://github.com/awslabs/mountpoint-s3/pull/622)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a bit understated. Should it be under something like ### New features
?
In terms of the text, maybe something like:
### New features
Introduced optional caching of object metadata and content,
in order to allow reduced cost and improved performance for repeated reads to the same files.
([#622](https://github.com/awslabs/mountpoint-s3/pull/622))
I'm also thinking when we merge the documentation, we can follow up too:
### New features
Introduced optional caching of object metadata and content,
in order to allow reduced cost and improved performance for repeated reads to the same files.
To get started, see the [caching section of the configuration documentation](https://github.com/awslabs/mountpoint-s3/blob/main/doc/CONFIGURATION.md#caching-configuration).
([#622](https://github.com/awslabs/mountpoint-s3/pull/622))
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jamesbornholt can you share feedback here too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agree we should put this in a new features section
Signed-off-by: Alessandro Passaro <[email protected]>
Signed-off-by: Alessandro Passaro <[email protected]>
62fb41f
to
4eb5fb0
Compare
Adopted @dannycjones suggestions and rebased to solve conflicts with |
Description of change
Remove the "caching" build feature. With this change, the new command line flag
--cache
and related options to support caching are generally available.Relevant issues: #255
Does this change impact existing behavior?
No. The new caching behavior is optional and needs to be explicitly enabled with a command line flag.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and I agree to the terms of the Developer Certificate of Origin (DCO).