Skip to content

Conversation

@EdwinEngelen
Copy link

Previously the timestamp did have a a precision of one second. The fraction got lost.
The timestamp is a double now and contains the fractions of a second.

Fixes #12

@EdwinEngelen EdwinEngelen force-pushed the master branch 2 times, most recently from 4d19ccb to 1bf1dfd Compare March 26, 2020 10:38
@EdwinEngelen
Copy link
Author

@moriyoshi or someone else, can you please review this?

Previously the timestamp did have a a precision of one second. The fraction got lost.

The timestamp is now of the EventTime time according to specification:
https://github.com/fluent/fluentd/wiki/Forward-Protocol-Specification-v1#eventtime-ext-format

EventTime has nanosecond precision, but .NET only supports 100 nanoseconds (ticks).

Fixes fluent#12

Signed-off-by: Edwin Engelen <edwin@engelen.name>
@EdwinEngelen EdwinEngelen changed the title Use timestamp with subsecond precision Send fractions of a second to Fluentd Mar 26, 2020

that.PackExtendedTypeValue(
0x0,
new[]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could be nice if it worked without additional byte[]-array allocation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Timestamp precision is missing fractions of a second

2 participants