Repository navigation
Conversation
Signed-off-by: Eduardo Silva <eduardo@chronosphere.io>
Signed-off-by: Eduardo Silva <eduardo@chronosphere.io>
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This branch had an error being deployed
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.
A SQL WHERE predicate applied to grouped OTLP logs also evaluates the resource/scope group markers. When those markers do not contain the queried field, SQL deletes them, and surviving logs lose their resource/scope metadata. Skip transport group markers and apply SQL predicates only to normal log records. Existing group normalization removes envelopes whose logs were all dropped.
For two resource groups containing ids 1–4,
SELECT * FROM STREAM WHERE id = 1;now retains id 1 with its original resource and scope, removes the empty second group, and reports one logical output record. This reproduces on unchanged master in both input and output processor contexts. No configuration or bundled-library changes; the performance optimization is a separate PR.Local validation
Focused commands from
tests/integration, withFLUENT_BIT_BINARYpointing at this branch's binary:ctest --test-dir build -R '^flb-it-(processor|processor_conditional|mp_chunk_cobj)$' --output-on-failureExample SQL processor:
Packaging/documentation: N/A. Target: master; no backport included.