-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
in_kafka: Fix in kafka json parsing #7492
Conversation
814aba8
to
d2f345a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should add this new setting to the documentation, especially if it changes the default behavior considering that before this plugin tried to decode json encoded data always (which is not the case anymore).
d2f345a
to
c2ce36f
Compare
Signed-off-by: Thiago Padilha <[email protected]>
This option allows automatic parsing of kafka messages payload with the specified format. Right now only "json" is supported. Signed-off-by: Thiago Padilha <[email protected]>
Signed-off-by: Thiago Padilha <[email protected]>
Signed-off-by: Thiago Padilha <[email protected]>
All good with the changes; just one minor ask, please change the config property from |
0c0634d
to
f7e999e
Compare
renamed the property @edsiper |
Signed-off-by: Thiago Padilha <[email protected]>
f7e999e
to
b3f5467
Compare
@tarruda where's the doc for the new |
fluent/fluent-bit-docs#1118 I just renamed
For now it is just "none" (no parsing, the default) and "json". Eventually we might support other formats such as avro |
Hello,
I use this conf:
Edit1: Neither |
@martinmajtan did you compile fluent-bit from latest master? I just ran the |
I should have mention I'm using Helm chart where I used image version 2.1.7. |
@martinmajtan this PR will only be available in version 2.1.8 |
|
This fixes json parsing for in_kafka, also add
data_format
configuration option, for explicit parsing control.Fixes #7481