forked from elastic/logstash
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Automatically choose most correct codec for bytestream inputs.
Now, if you try to use `plain` or `json` codecs with either `stdin` or `tcp` inputs, it will automatically select `line` or `json_lines` codec respectively. Right now, many users try to use json codec with tcp input. This *should* work, but due to technical limitations[1], it does not. To compensate, we have always provided a json_lines codec to help parse "streams of line-delimited json" which is what most folks seem to be handling these days. [1] I haven't found a JSON library capable of processing a byte stream. Jackson has one, but it requires an input stream model which logstash does not currently expose. Future work will make this possible. Related: elastic#1391
- Loading branch information
1 parent
ab9985c
commit 4d64691
Showing
3 changed files
with
18 additions
and
0 deletions.
There are no files selected for viewing
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
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
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