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.
curl --progress-bar "http://127.0.0.1:9200/index-logs1/_field_caps?fields=*" | jq '.fields' | grep -E '^ "' 2>/dev/null | grep metadata | awk -F. '{print NF}' | sort -n | wc -l
733
curl --progress-bar "http://127.0.0.1:9200/index-logs1/_field_caps?fields=*" | jq '.fields' | grep -E '^ "' 2>/dev/null | grep context | awk -F. '{print NF}' | sort -n | wc -l
218
But if i could limit nesting level for parsing, it would dramatically decreased fields count:
curl --progress-bar "http://127.0.0.1:9200/index-logs1/_field_caps?fields=*" | jq '.fields' | grep -E '^ "' 2>/dev/null | grep metadata | awk -F. 'NF>5 {print NF}' | sort -n | wc -l
101
curl --progress-bar "http://127.0.0.1:9200/index-logs1/_field_caps?fields=*" | jq '.fields' | grep -E '^ "' 2>/dev/null | grep context | awk -F. 'NF>5 {print NF}' | sort -n | wc -l
25
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:
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: