fix: parse large file with resolve option set to true #2258
+86,259
−102
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.
Description
The fix separates YAML parsing from data mapping: the YAML text is first parsed using SnakeYAML with increased safety limits.
The resulting Java object structure is then converted to a JsonNode using the existing mapper, without Jackson parsing the YAML itself.
This avoids Jackson YAML size/depth limits while preserving all existing mapper configuration and behavior.
Fix for #2059
Type of Change
Checklist
Screenshots / Additional Context