clean up field-reference-parser#12466
Conversation
| //NOTE: The notable-breaking-changes tagged regions are re-used in the | ||
| //Installation and Upgrade Guide | ||
|
|
||
| [[breaking-8.0]] |
There was a problem hiding this comment.
@karenzone I should cc you before merging it 😨
Could you review the doc? This PR is a breaking change of removing --field-reference-parser
karenzone
left a comment
karenzone
left a comment
There was a problem hiding this comment.
I offered some minor wording changes in line for your consideration.
What you have does not break the build, and will be acceptable for now if you choose not to make the changes now.
| The Field Reference parser by default was STRICT in version 7. This configuration is removed permanently. | ||
| Logstash keeps the behaviour as if the default setting, which interprets references to fields in your pipelines and plugins, | ||
| and rejects inputs that are either ambiguous or illegal. | ||
|
|
There was a problem hiding this comment.
What about:
"The Field Reference parser interprets references to fields in your pipelines and
plugins. It was configurable in 7.x, with the default set to strict to reject
inputs that are ambiguous or illegal. Configurability is removed in 8.0. Now
{ls] rejects ambiguous and illegal inputs as standard behavior."
4 participants
Fixed: #12355
remove field-reference-parser for version 8