Skip to content

Allow disabling splitting original message to lines#21

Open
sxmichael wants to merge 1 commit into
logstash-plugins:mainfrom
sxmichael:master
Open

Allow disabling splitting original message to lines#21
sxmichael wants to merge 1 commit into
logstash-plugins:mainfrom
sxmichael:master

Conversation

@sxmichael

@sxmichael sxmichael commented Jan 15, 2016

Copy link
Copy Markdown

Sometimes it's necessary to join multiple messages from the input, without splitting the original message by new lines (example: joining es bulk api input messages)

@ghost

ghost commented Jan 17, 2016

Copy link
Copy Markdown

Jenkins standing by to test this. If you aren't a maintainer, you can ignore this comment. Someone with commit access, please review this and clear it for Jenkins to run; then say 'jenkins, test it'.

@sxmichael sxmichael force-pushed the master branch 3 times, most recently from 7283f0d to 809049f Compare August 6, 2016 11:09
Added split_original config param (default: true), when true - splits the original message to multiple lines by '\n'; when false - passes original message as is.
over_maximun_lines check changed from 'greater then' to 'greater or equal': setting max_lines = X actually produced message blocks of X+1 messages due to strict "greater than" sign.
@sxmichael

Copy link
Copy Markdown
Author

Could this be merged?

@sxmichael

Copy link
Copy Markdown
Author

any update?

@jordansissel

Copy link
Copy Markdown
Contributor

@sxmichael Sorry for the very long delays.

I don't understand what problem this code is solving. Multiline is a line-oriented concept, so splitting by line on the input payload makes sense to me (example: tcp input can read large chunks of text that include multiple, possibly unrelated, lines).

Your example of ES bulk api isn't clear enough to me to understand what you need. Can you tell me a story or describe a use case?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants