Fix queue.max_bytes field in logstash pipeline settings spec
#3925
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
💚 CLA has been signed |
kaiwenleee
force-pushed
the
fix/logstash-pipeline-settings
branch
from
6dd84f2 to
84b7e8c
Compare
kaiwenleee
force-pushed
the
fix/logstash-pipeline-settings
branch
from
84b7e8c to
c6dd8eb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Logstash
PipelineSettingsis usingqueue.max_bytessince at least 6.0 rather thanqueue.max_bytes.number&queue.max_bytes.units. This is also shown in the example.Updating the spec so that elasticsearch clients can work correctly.
ref: elastic/elasticsearch#92651