THRIFT-4555 Optionally disable copies of binary fields in Java constructors, getters, and setters #1540
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.
THRIFT-2233 added safeguards when working with binary fields by performing TBaseHelper.copyBinary on the input bytes in relevant constructors, getters and setters in the Java client. While this is safer, it incurs a heavy overhead cost in GC churn by unnecessarily creating and destroying byte arrays when the input does happen to be safe.
This PR introduces a flag to disable these copies of binary fields, to improve performance in situations where developers are sure that the input (or output) will not later be mutated.
This builds without issue for me locally. This does not currently have any tests; I can add tests if this new flag is plausibly acceptable to the maintainers.