-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
null value fields are dropped from JSON decoding #5522
Comments
It's probably not the JSON decoder. Beats drop null values as part of the output process. |
@andrewkroh The null value mapping is an handy settings we could allow user to configure that behavior? @PhaedrusTheGreek an ingest pipeline could be a workaround for now, the downside is this might be more costly on space than the null value mapping? I don't know how this is implemented. |
Yes, we could workaround in Logstash, but there is a lot of re-determination of information already present then lost from the original JSON document that would lead to inefficiencies in processing, space savings, maintenance/management, etc. We might prefer to wait for a fix if it's foreseeable. |
Just to update this issue, we have decided to keep the current behavior as the default and add an opt-in flag to retain null values. |
What PR was this added in ? |
Was this added? @ph |
i am sending my json to logsatsh why do event is dropped at filebeat ? how to handle it ? |
Not yet, I will resurrect that. |
Hello, guys! |
Given a file like this:
With the following FB config:
The
test-null
field is dropped before being sent to ES:While hoping to make use of Elasticsearch's null_value mapping parameter.
The text was updated successfully, but these errors were encountered: