chore(engine): Add compatibility node for parsed columns #19485
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chaudum
requested review from
ivkalita,
rfratto,
sophiewaldman and
trevorwhitney
ivkalita
approved these changes
Oct 13, 2025
chaudum
force-pushed
the
chaudum/parsed-extracted
branch
from
eeddc56 to
0e7e117
Compare
After parsing log lines, field names need to be checked whether they collide with label field names. Follow up on #19470
Co-authored-by: Ivan Kalita <[email protected]> Signed-off-by: Christian Haudum <[email protected]>
Co-authored-by: Ivan Kalita <[email protected]> Signed-off-by: Christian Haudum <[email protected]>
chaudum
force-pushed
the
chaudum/parsed-extracted
branch
from
a7bcb80 to
06df9a8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary
The v1 engine has a mechanism to rename labels in case they have the same name but different origin, such as labels, structured metadata, or parsed fields.
_extracted, such asservice_extracted, ifserviceexists in bothlabelsandmetadata._extractedin the same way as case 1. However, if the field name also collides with a structured metadata key, then the extracted structured metadata is replaced with the extracted parsed field.This PR only implements the second case.
This PR is a follow up on #19470