You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use UTC timestamps when we write logs in Kafka, and date partitioning on S3.
When I tried to parse a timestamp column like { "@t": "2020-11-11T07:58:58.7291622Z" }, generated filename was 20201110_22xx (GMT+9), not 20201111_07xx!
in-kafka-group creates TimeParser with just time_format, since there is no parameter like utc.
We use UTC timestamps when we write logs in Kafka, and date partitioning on S3.
When I tried to parse a timestamp column like
{ "@t": "2020-11-11T07:58:58.7291622Z" }
, generated filename was20201110_22xx
(GMT+9), not20201111_07xx
!in-kafka-group
creates TimeParser with justtime_format
, since there is no parameter likeutc
.fluent-plugin-kafka/lib/fluent/plugin/in_kafka_group.rb
Lines 134 to 140 in fe1d71e
TimeParser uses local time by default. (
localtime = true
)https://github.com/fluent/fluentd/blob/6757d70b7fdfcf5e4a6316b1ecd802dfeb0e326e/lib/fluent/time.rb#L208
Can we have
utc
parameter like parsers? When I settime_source
askafka
, it worked properly. The timestamp was UTC.The text was updated successfully, but these errors were encountered: