This repository was archived by the owner on May 17, 2019. It is now read-only.
parser_json: Document new stream_buffer_size param #631
Conversation
This file contains hidden or 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
benwh
force-pushed
the
document-stream-buffer-size
branch
from
2f681b3 to
acc46a0
Compare
See fluent/fluentd#2381 In addition to documenting the parameter, update the `in_exec` and `out_exec_filter` articles to provide a workaround for users encountering this problem. This note exists in the v0.12 version of the `in_exec` page but was absent in the v1.0 docs, so add the whole note. Closes fluent#624 Signed-off-by: Ben Wheatley <[email protected]>
benwh
force-pushed
the
document-stream-buffer-size
branch
from
acc46a0 to
7eca11e
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
See fluent/fluentd#2381
In addition to documenting the parameter, update the
in_execandout_exec_filterarticles to provide a workaround for usersencountering this problem.
This note exists in the v0.12 version of the
in_execpage but wasabsent in the v1.0 docs, so add the whole note.
Closes #624
Signed-off-by: Ben Wheatley [email protected]