Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Double @timestamp key when using the JSON decoder #5437

Closed
3 of 4 tasks
tsg opened this issue Oct 25, 2017 · 2 comments
Closed
3 of 4 tasks

Double @timestamp key when using the JSON decoder #5437

tsg opened this issue Oct 25, 2017 · 2 comments
Labels
bug Filebeat Filebeat meta

Comments

@tsg
Copy link
Contributor

tsg commented Oct 25, 2017 •
edited by urso
Loading

Initially reported on discuss, the bug is about adding two @timestamp keys when using JSON decoding on a doc that has a valid @timestamp key in it.
@kvch
Copy link
Contributor

kvch commented Oct 25, 2017

An issue for the initial bug is opened: #5440

@tsg tsg mentioned this issue Oct 25, 2017
Closed
tsg added a commit to tsg/beats that referenced this issue Oct 26, 2017
@tsg
Catch duplicate keys in integration tests
6b23236 
This enabled duplicate key detection when we read the results in
the system tests. This makes sure that if we ever have a duplicate key
like in elastic#5440 we will notice.

Part of elastic#5437.
@tsg tsg mentioned this issue Oct 26, 2017
Merged
andrewkroh pushed a commit that referenced this issue Oct 30, 2017
@tsg @andrewkroh
Catch duplicate keys in integration tests (#5455)
7fad7f3 
* Catch duplicate keys in integration tests

This enabled duplicate key detection when we read the results in
the system tests. This makes sure that if we ever have a duplicate key
like in #5440 we will notice.

Part of #5437.
@kvch kvch closed this as completed Dec 20, 2019
@kvch
Copy link
Contributor

kvch commented Dec 20, 2019

Resolved in later versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Filebeat Filebeat meta
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tsg @kvch