Skip to content

Numeric time stamp causes time_key parsing to fail #3

@raoul189

Description

@raoul189

If time_stamp is declared for a particular field in the JSON, and the field is an integer e.g. {"ts":1435527344}, and the time_format is declared as %s, the burrow plugin passes the values to the fluent parser but the fluent parser fails:

time_key ts
time_format %s

error_class=Fluent::ParserError error="value must be string: 1435527344"

The integer should be processed as a valid strftime epoch time stamp similar to:
% date -u --date=@1435527344
Sun Jun 28 21:35:44 UTC 2015

burrow may need to change the type in case of integer time stamps before submitting.

Thank you!

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions