Skip to content

Cherry-pick #8346 to 6.4: Correctly parse rfc3339 timezone and Nanosecond#8432

Merged
ph merged 1 commit intoelastic:6.4from
ph:backport_8346_6.4
Sep 25, 2018
Merged

Cherry-pick #8346 to 6.4: Correctly parse rfc3339 timezone and Nanosecond#8432
ph merged 1 commit intoelastic:6.4from
ph:backport_8346_6.4

Conversation

@ph
Copy link
Copy Markdown
Contributor

@ph ph commented Sep 25, 2018

Cherry-pick of PR #8346 to 6.4 branch. Original message:

The code was not correctly creating the time and was isntead making
events appear to be a few years in the future. The nanosecond extraction
was not on the right scale for the time.Date, the commit fixes the
behavior and do assertions with the go parser.

bug was reported by @vjsamuel

* Correctly parse rfc3339 timezone and Nanosecond

The code was not correctly creating the time and was isntead making
events appear to be a few years in the future. The nanosecond extraction
was not on the right scale for the time.Date, the commit fixes the
behavior and do assertions with the go parser.

(cherry picked from commit 6204fce)
@ph ph merged commit 7130a46 into elastic:6.4 Sep 25, 2018
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
… Nanosecond (elastic#8432)

Cherry-pick of PR elastic#8346 to 6.4 branch. Original message: 

The code was not correctly creating the time and was isntead making
events appear to be a few years in the future. The nanosecond extraction
was not on the right scale for the time.Date, the commit fixes the
behavior and do assertions with the go parser.

bug was reported by @vjsamuel
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.

2 participants