Skip to content

Commit c3c1e45

Browse files
Update pipeline/inputs/tail.md
Co-authored-by: Alexa Kreizinger <[email protected]> Signed-off-by: Hiroshi Hatake <[email protected]>
1 parent 0216013 commit c3c1e45

File tree

1 file changed

+3
-7
lines changed

1 file changed

+3
-7
lines changed

pipeline/inputs/tail.md

Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -44,13 +44,9 @@ If the database parameter `DB` isn't specified, by default the plugin reads each
4444
{% endhint %}
4545

4646
{% hint style="info" %}
47-
Note that `Unicode.Encoding` depends on simdutf library which is written in C++11 or above.
48-
So, the older platforms are not supported for this feature.
49-
In addition, `Unicode.Encoding auto` is not covered for the all of the usages.
50-
This is because sometimes this auto-detecting for character encodings makes a mistake to guess the correct encoding.
51-
We recommend to use `UTF-16LE` or `UTF-16BE` if the target file encoding is pre-determined or known beforehand.
52-
In details, this parameter requests to use 2-bytes aligned chunk and buffer sizes.
53-
If they are not aligned for 2 bytes, Fluent Bit will use 2-bytes alignments automatically to avoid character breakages on consuming boundaries.
47+
The `Unicode.Encoding` parameter is dependent on the simdutf library, which is itself dependent on C++ version 11 or later. In environments that use earlier versions of C++, the `Unicode.Encoding` parameter will fail.
48+
49+
Additionally, the `auto` setting for `Unicode.Encoding` isn't supported in all cases, and can make mistakes when it tries to guess the correct encoding. For best results, use either the `UTF-16LE` or `UTF-16BE` setting if you know the encoding type of the target file.
5450
{% endhint %}
5551

5652
## Monitor a large number of files

0 commit comments

Comments
 (0)