This repository has been archived by the owner on Jun 1, 2024. It is now read-only.
Issue nr: 14594 - removing old implementation where fields where dot-… #351
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…escaped due to old ELK not supporting it. But now this is supported, therefore there is no need to escape it anylonger.
What issue does this PR address?
Disable dot escaping for field names, as it is supported since long time ago in ELK.
Does this PR introduce a breaking change?
If the field name
x.y
was used, till now in kibana it would show asx/y
, after this commit, it will show asx.y
. But I think the breaking change is very small.Please check if the PR fulfills these requirements
There was no need for new unit tests, since only old code was removed.
Other information:
Also changed a method from using recursion to a simple while loop.