Minor: avoid an Arc::clone in CacheOptions for Parquet PredicateCache
#8338
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.
Which issue does this PR close?
Rationale for this change
I found this while working on #7997
Basically, the fact that the CacheOptionsBuilder had both owned and non owned fields made it a bit akward to work with -- if it is going to be zero copy (references) we pay the price of tracking lifetimes already. We may as well just do so for the Arc as well
I don't expect this to make any measurable different in performance. I am mostly treating it as a cleanup
What changes are included in this PR?
Remove one Arc::clone
Are these changes tested?
By existing CI
If tests are not included in your PR, please explain why (for example, are they covered by existing tests)?
Are there any user-facing changes?
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 call them out.