Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Caching conflict when creating CSV schemas with different views for the same POJO
See original GitHub issue#195 added csv schema creation with views. Using the same CsvMapper with the same POJO for different views leads to unexpected results as the used view is not considered when a schema is loaded from cache as it was registered for the pojoType. Obviously, the used view should be part of the key for the cache maps _untypedSchemas and _typedSchemas.
Edit: A workaround is quite simple. In order to clear the cache, just use csvmapper.copy().schemaForWithView(...) instead of csvmapper.schemaForWithView(...).
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
2.14: keeping caching simple for 2.13 patch just in case.
There isn’t a lot about contributing, just this:
https://github.com/FasterXML/jackson/blob/master/CONTRIBUTING.md
Sure, I can try to find some time. Should I create a PR based on
2.13or2.14? Are there any contribution guide lines?