[8.x] Reimplement LogStash::Numeric setting in Java (backport #17127) #17273
+137
−35
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.
Release notes
[rn:skip]
What does this PR do?
Reimplements
LogStash::Setting::Numeric
Ruby setting class into theorg.logstash.settings.NumericSetting
and exposes it throughjava_import
asLogStash::Setting::NumericSetting
.Updates the rspec tests:
java.lang.IllegalArgumentException
instead ofArgumentError
is thrown because the kind of exception thrown by Java code, during verification.Why is it important/What is the impact to the user?
As a developer I want use Java classes to shape the configuration settings.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files (and/or docker env variables)Author's Checklist
How to test this PR locally
Update a numeric settings like
pipeline.batch.delay
to a value that's not the default, start Logstash and verify that the setting value is used, for example check withRelated issues
This is an automatic backport of pull request Reimplement LogStash::Numeric setting in Java #17127 done by Mergify.