-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Max nesting level for json parser #3311
Comments
One more question: |
It seems there is no way to do it (pull request is welcome 😄)
It seems that oj is optional, it ensures to use oj if it's available but not required mandatory. Line 23 in 6a2852a
Line 52 in 6a2852a
fluentd/lib/fluent/plugin/parser_json.rb Lines 61 to 71 in 6a2852a
In addition, there is the following description about yajl in the document of this plugin:
|
However, it surely confusing. Because it's not documented, users can't understand such behavior. |
|
Fixed by #3315 |
Now I've noticed that It's reported at https://app.slack.com/client/T0CSKNZLK/C0CTT63EE/thread/C0CTT63EE-1631532462.067500 We should consider other way to apply it. |
Does FLUENT_OJ_OPTION_MAX_NESTING still doesn't work? |
Yes, it doesn't work. Because now I notice that |
The implementation of Oj:
|
This option doesn't take effect in actual since the global setting `Oj.default_options` doesn't accept `max_nesting`. It should be specified by each instances. #3311 (comment) Signed-off-by: Takuro Ashie <[email protected]>
This option doesn't take effect in actual since the global setting `Oj.default_options` doesn't accept `max_nesting`. It should be specified by each instances. #3311 (comment) Signed-off-by: Takuro Ashie <[email protected]>
This option doesn't take effect in actual since the global setting `Oj.default_options` doesn't accept `max_nesting`. It should be specified by each instances. #3311 (comment) Signed-off-by: Takuro Ashie <[email protected]>
Is your feature request related to a problem? Please describe.
I want to have option for the json parser plugin to limit nesting level for the parsing.
My developers send huge metadata json, after parsing it "eats" elasticsearch fields.
But if i could limit nesting level for parsing, it would dramatically decreased fields count:
Describe the solution you'd like
Set parameter to json parser section -
max_nesting(int)
So the parser would leave unparsed json after the nesting is reacher.
Describe alternatives you've considered
Additional context
As i can see, parameter support with main json ruby libraries:
The text was updated successfully, but these errors were encountered: