CSV schema caching POJOs with different views #297
Merged
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.
This PR adds caching of CSV schemas for POJOs with views once they have been created (see #288).
CsvMapper.ViewKey
as cache keySchemaCaching288Test
fromcom.fasterxml.jackson.dataformat.csv.schema
tocom.fasterxml.jackson.dataformat.csv
in order to check cache usage via sizeCsvMapper.ViewKey
uses bothObjects.equals()
andObjects.hashCode()
. Is this acceptable or should it be changed?You would have to decide whether access modifiers for
CsvMapper.ViewKey
should be changed and whether it would be better defined as a top-level class.