From ce0b1d27bbc162d007bef9f958cf564cecb4e8ab Mon Sep 17 00:00:00 2001 From: Satvik Mishra Date: Fri, 9 Oct 2026 09:57:18 +0530 Subject: [PATCH] docs(filter/parser): fix swapped reserve_time examples When reserve_time is true, Fluentd keeps the original event time and discards the parsed time; when false (default), the parsed time is used. The examples previously showed the opposite. Matches filter_parser.rb. Fixes #439 Signed-off-by: Satvik Mishra --- filter/parser.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/filter/parser.md b/filter/parser.md index 6db1a50b..e3636e05 100644 --- a/filter/parser.md +++ b/filter/parser.md @@ -97,7 +97,7 @@ Above incoming event is parsed as: ```text time: -2021-06-01 00:00:00.000000000 +0900 +2021-06-24 14:33:35.475115751 +0900 (It varies — original event time) record: { @@ -105,7 +105,7 @@ record: } ``` -The value of `time` field \(`1622473200`\) is reserved as event time \(`2021-06-01 00:00:00.000000000 +0900`\). +The original event time is kept. The value of the parsed `time` field \(`1622473200`\) is discarded as event time. Without `reserve_time`, the result is: @@ -117,7 +117,7 @@ Above incoming event is parsed as: ```text time: -2021-06-24 14:33:35.475115751 +0900 (It varies on parsed timestamp) +2021-06-01 00:00:00.000000000 +0900 record: { @@ -125,7 +125,7 @@ record: } ``` -The value of parsed timestamp is set as event time. The value of `time` field is discarded. +The value of the `time` field \(`1622473200`\) is set as event time \(`2021-06-01 00:00:00.000000000 +0900`\). ### `reserve_data`