-
Notifications
You must be signed in to change notification settings - Fork 115
Fix queue.max_bytes field in logstash pipeline settings spec
#3925
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
Fix queue.max_bytes field in logstash pipeline settings spec
#3925
Conversation
|
💚 CLA has been signed |
84b7e8c to
c6dd8eb
Compare
9791615 to
a42857e
Compare
a42857e to
599c027
Compare
|
Hello, can any maintainer take a look at the PR, or is there something I'm missing? I did look at the contribution instruction but don't see a clear gap, except that it's no longer possible to do the validation part since |
|
hey @kaiwenleee, thanks for contributing! validation is not starting since it doesn't work for forks, I'll open a mirror PR just to start validation. |
|
so, turns out we're missing tests for this API ^^" but it looks correct, also this server test confirms it. LGTM, thanks again! |
Co-authored-by: Wenkai Li <wenkai.li@ing.com> Co-authored-by: Laura Trotta <153528055+l-trotta@users.noreply.github.com> (cherry picked from commit 1403bac)
Co-authored-by: Wenkai Li <wenkai.li@ing.com> Co-authored-by: Laura Trotta <153528055+l-trotta@users.noreply.github.com> (cherry picked from commit 1403bac)
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