-
Notifications
You must be signed in to change notification settings - Fork 540
Add json.escape_unicode option to service configuration #2131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
50b5c77 to
35afdc1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
json.escape_unicode handles boolean value. So,we need to use with On/true or Off/false for specifying escaping non-ASCII characters with Unicode code points.
administration/configuring-fluent-bit/classic-mode/configuration-file.md
Outdated
Show resolved
Hide resolved
administration/configuring-fluent-bit/yaml/configuration-file.md
Outdated
Show resolved
Hide resolved
|
@owanio1992 Could you add Signed-off line in your commit? Under the fluent organization repos, we request to use commit signs for every contributors. |
7327cc7 to
99100bd
Compare
|
I'll come back for a tech writing review once @cosmo0920 's requested changes are done =) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For technical perspective, it looks good.
But DCO still complains that the author and the commiter information differs like:
Commit sha: 99100bd, Author: owan, Committer: owan; Expected "owan chihhao.wang@zyxel.com.tw", but got "owanio1992 owan.io1992@gmail.com".
|
@owanio1992 if you can look at the DCO failures this can be reviewed by @esmerel. |
b745e02 to
2a4e588
Compare
2e06f6b to
9daaeb3
Compare
Signed-off-by: owanio1992 <owan.io1992@gmail.com>
9daaeb3 to
9c63970
Compare
|
@cosmo0920 I update description and default value, please review again |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
3 comments, same question on each. otherwise this looks fine to me
| | `scheduler.cap` | Set a maximum retry time in seconds. Supported in v1.8.7 and greater. | `2000` | | ||
| | `scheduler.base` | Set a base of exponential backoff. Supported in v1.8.7 and greater. | `5` | | ||
| | `json.convert_nan_to_null` | If enabled, `NaN` converts to `null` when Fluent Bit converts `msgpack` to `json`. | `false` | | ||
| | `json.escape_unicode` | Controls how Fluent Bit serializes non‑ASCII / multi‑byte Unicode characters in JSON strings. When enabled, Unicode characters are escaped as \uXXXX sequences (characters outside BMP become surrogate pairs). When disabled, Fluent Bit emits raw UTF‑8 bytes. | `true` | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| | `json.escape_unicode` | Controls how Fluent Bit serializes non‑ASCII / multi‑byte Unicode characters in JSON strings. When enabled, Unicode characters are escaped as \uXXXX sequences (characters outside BMP become surrogate pairs). When disabled, Fluent Bit emits raw UTF‑8 bytes. | `true` | | |
| | `json.escape_unicode` | Controls how Fluent Bit serializes non‑ASCII / multi‑byte Unicode characters in JSON strings. When enabled, Unicode characters are escaped as `\uXXXX` sequences (characters outside BMP become surrogate pairs). When disabled, Fluent Bit emits raw UTF‑8 bytes. | `true` | |
This probably should be in code fence, but I'm not sure if the escape character needs to be in there or not
| | `scheduler.cap` | Set a maximum retry time in seconds. Supported from v1.8.7. | `2000` | | ||
| | `scheduler.base` | Sets the base of exponential backoff. Supported from v1.8.7. | `5` | | ||
| | `json.convert_nan_to_null` | If enabled, NaN is converted to null when Fluent Bit converts `msgpack` to JSON. | `false` | | ||
| | `json.escape_unicode` | Controls how Fluent Bit serializes non‑ASCII / multi‑byte Unicode characters in JSON strings. When enabled, Unicode characters are escaped as \uXXXX sequences (characters outside BMP become surrogate pairs). When disabled, Fluent Bit emits raw UTF‑8 bytes. | `true` | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| | `json.escape_unicode` | Controls how Fluent Bit serializes non‑ASCII / multi‑byte Unicode characters in JSON strings. When enabled, Unicode characters are escaped as \uXXXX sequences (characters outside BMP become surrogate pairs). When disabled, Fluent Bit emits raw UTF‑8 bytes. | `true` | | |
| | `json.escape_unicode` | Controls how Fluent Bit serializes non‑ASCII / multi‑byte Unicode characters in JSON strings. When enabled, Unicode characters are escaped as `\uXXXX` sequences (characters outside BMP become surrogate pairs). When disabled, Fluent Bit emits raw UTF‑8 bytes. | `true` | |
same here
| | `scheduler.cap` | Sets a maximum retry time in seconds. Supported in v1.8.7 and greater. | `2000` | | ||
| | `scheduler.base` | Sets the base of exponential backoff. Supported in v1.8.7 and greater. | `5` | | ||
| | `json.convert_nan_to_null` | If enabled, `NaN` is converted to `null` when Fluent Bit converts `msgpack` to `json`. | `false` | | ||
| | `json.escape_unicode` | Controls how Fluent Bit serializes non‑ASCII / multi‑byte Unicode characters in JSON strings. When enabled, Unicode characters are escaped as \uXXXX sequences (characters outside BMP become surrogate pairs). When disabled, Fluent Bit emits raw UTF‑8 bytes. | `true` | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| | `json.escape_unicode` | Controls how Fluent Bit serializes non‑ASCII / multi‑byte Unicode characters in JSON strings. When enabled, Unicode characters are escaped as \uXXXX sequences (characters outside BMP become surrogate pairs). When disabled, Fluent Bit emits raw UTF‑8 bytes. | `true` | | |
| | `json.escape_unicode` | Controls how Fluent Bit serializes non‑ASCII / multi‑byte Unicode characters in JSON strings. When enabled, Unicode characters are escaped as `\uXXXX` sequences (characters outside BMP become surrogate pairs). When disabled, Fluent Bit emits raw UTF‑8 bytes. | `true` | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For technical side, it looks good to me. Thank you for your contribution.
feature source PR: fluent/fluent-bit#10665
This commit adds the
json.escape_unicodeoption to the service configuration for both classic and YAML modes.This option allows users to control the encoding of raw UTF-8 strings when serializing MessagePack records to JSON.