-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Apply Jackson stream read constraints defaults at runtime #16832
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -18,6 +18,14 @@ public class StreamReadConstraintsUtil { | |
|
||
private StreamReadConstraints configuredStreamReadConstraints; | ||
|
||
// Provide default values for Jackson constraints in the case they are | ||
// not specified in configuration file. | ||
private static final Map<Override, Integer> JACKSON_DEFAULTS = Map.of( | ||
Override.MAX_STRING_LENGTH, 200_000_000, | ||
Override.MAX_NUMBER_LENGTH, 10_000, | ||
Override.MAX_NESTING_DEPTH, 1_000 | ||
); | ||
|
||
enum Override { | ||
MAX_STRING_LENGTH(StreamReadConstraints.Builder::maxStringLength, StreamReadConstraints::getMaxStringLength), | ||
MAX_NUMBER_LENGTH(StreamReadConstraints.Builder::maxNumberLength, StreamReadConstraints::getMaxNumberLength), | ||
|
@@ -78,6 +86,8 @@ StreamReadConstraints get() { | |
if (configuredStreamReadConstraints == null) { | ||
final StreamReadConstraints.Builder builder = StreamReadConstraints.defaults().rebuild(); | ||
|
||
// Apply the Jackson defaults first, then the overrides from config | ||
JACKSON_DEFAULTS.forEach((override, value) -> override.applicator.apply(builder, value)); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. My biggest worry with these kind of changes is how to educate users to keep settings up to date.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I was thinking this approach removed the need for user's to worry about this at all. In all the cases you mentioned they never cared about this setting and now they can continue to not care about it. They only have to think about it if they are in a situation where they explicitly need to tune it. But maybe i'm not quite understanding your concern? |
||
eachOverride((override, value) -> override.applicator.apply(builder, value)); | ||
|
||
this.configuredStreamReadConstraints = builder.build(); | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CODEREVIEW: I just noticed this is actually not set explicitly
logstash/config/jvm.options
Line 90 in 0eb03ad
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@edmocosta Is it intended to comment out? I think it is supposed to be uncommented
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it's intended to be commented out, at time we added those properties,
1000
was the default value already, and we haven't had any problem with that specific limit that would justify overriding it.It seems the Jackson's team is still tuning it, and the new default value was reduced to
500
(FasterXML/jackson-core#1234). They've a good reasoning on why it was reduced (FasterXML/jackson-core#1233), but I think we can be more conservative and sticky to the well tested1000
(at least for now). With this new code, it seems uncommenting the property wouldn't make much difference, so I'm fine with whatever you folks think is better.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, keeping the comment is good to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow it sounds we lost consistency here as well.
Do we know till which jackson version (and LS version) we had nesting-depth with 1000 and which version decreased to 500 in which LS version? Do we have issues reported for such situation? If so, addressing separately would be good idea considering user stories.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new default value will be released in
3.0
, so we should be fine now and after upgrading (thanks to this PR).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, my comment was very ambiguous after reading it following a break 😅
My question is given we have this commented out should I remove the default from being applied. I was not suggesting we remove the example from the options file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO, I'd keep it, it's a no-op for now, but knowing that Jackson will reduce this limit in the near future, setting it here would ensure that all defaults values are aligned with Logstash's requirements.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with @edmocosta here - let's keep it. While I wouldn't expect the upcoming changes in Jackson defaults to 500 to impact us, this will retain consistency with what we know is already working.