Add support for schema key aliases in query engine Parsers#1725
Merged
drewrelmas merged 12 commits intoopen-telemetry:mainfrom Feb 11, 2026
Merged
Add support for schema key aliases in query engine Parsers#1725drewrelmas merged 12 commits intoopen-telemetry:mainfrom
drewrelmas merged 12 commits intoopen-telemetry:mainfrom
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #1725 +/- ##
==========================================
+ Coverage 86.26% 86.27% +0.01%
==========================================
Files 525 525
Lines 165063 165273 +210
==========================================
+ Hits 142384 142595 +211
+ Misses 22145 22144 -1
Partials 534 534
🚀 New features to boost your workflow:
|
CodeBlanch
reviewed
Jan 6, 2026
CodeBlanch
reviewed
Jan 6, 2026
CodeBlanch
reviewed
Jan 6, 2026
CodeBlanch
reviewed
Jan 6, 2026
This was referenced Jan 6, 2026
|
This pull request has been marked as stale due to lack of recent activity. It will be closed in 30 days if no further activity occurs. If this PR is still relevant, please comment or push new commits to keep it active. |
CodeBlanch
reviewed
Feb 10, 2026
66a2019 to
a028eef
Compare
jmacd
approved these changes
Feb 10, 2026
Merged
via the queue into
open-telemetry:main
with commit Feb 11, 2026
0d0af9a
61 of 62 checks passed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Draft PR to open discussion - The current
otlp-bridgefor therecordsetengine uses the OpenTelemetry log data model spec for its initial schema keys (Attributes,Timestamp,ObservedTimestamp,SeverityText, etc).However, many well-versed in the OpenTelemetry space may be more used to the snake case representation (
attributes,time_unix_nano,observed_time_unix_nano,severity_text, etc) from the proto representation.Do we have any significant risks if we plan to support both? Inspired by
severity_textreference in #1722, been on the back of my mind for a while.This is still somewhat incomplete, could need more wiring for user-provided aliases in bridge, but for the moment just doing it for known OpenTelemetry fields.