[receiver/filelog] fix record counting with header #35870
Merged
Conversation
This file contains 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
This refactors the `Reader::ReadToEnd` method by separating reading the file's header from reading the file's contents. This results in very similar code in `readHeader` and `readContents` methods, which was previosly deduplicated at the cost of slightly higher complexity. The bug could be fixed without separating header reading from contents reading, but I hope this separation will make it easier to implement content batching in the Reader (open-telemetry#35455). Content batching was my original motivation for these code changes. I only discovered the problem with record counting when reading the code.
andrzej-stencel
commented
Oct 18, 2024
andrzej-stencel
commented
Oct 18, 2024
|
|
||
| // Switch to the normal split and process functions. | ||
| r.splitFunc = r.lineSplitFunc | ||
| r.processFunc = r.emitFunc |
There was a problem hiding this comment.
This "juggling" of function references could probably be avoided altogether after the refactoring.
The feature gate `AllowHeaderMetadataParsing` is currently in Beta stage, which means it is enabled by default. Some tests were still explicitly enabling the feature gate on test start and disabling it on test end, which would cause other tests to fail that expected the feature gate to be enabled.
djaglowski
reviewed
Oct 24, 2024
I have no idea why I left it in the ReadToEnd function.
djaglowski
approved these changes
Oct 28, 2024
jpbarto
pushed a commit
to jpbarto/opentelemetry-collector-contrib
that referenced
this pull request
Oct 29, 2024
) #### Description Fixes open-telemetry#35869 by refactoring of the `Reader::ReadToEnd` method. This refactors the `Reader::ReadToEnd` method by separating reading the file's header from reading the file's contents. This results in very similar code in `readHeader` and `readContents` methods, which was previously deduplicated at the cost of slightly higher complexity. The bug could be fixed without separating header reading from contents reading, but I hope this separation will make it easier to implement content batching in the Reader (open-telemetry#35455). Content batching was my original motivation for these code changes. I only discovered the problem with record counting when reading the code. #### Link to tracking issue Fixes open-telemetry#35869 #### Testing In the first commit I have added tests that document the erroneous behavior. In the second commit I have fixed the bug and corrected the tests. #### Documentation Added changelog entry.
andrzej-stencel
added a commit
to andrzej-stencel/opentelemetry-collector-contrib
that referenced
this pull request
Oct 31, 2024
Separates header processing functions from content processing functions to improve code clarity. This is a follow-up from open-telemetry#35870 (comment).
andrzej-stencel
added a commit
to andrzej-stencel/opentelemetry-collector-contrib
that referenced
this pull request
Oct 31, 2024
Separates header processing functions from content processing functions to improve code clarity. This is a follow-up from open-telemetry#35870 (comment).
andrzej-stencel
added a commit
to andrzej-stencel/opentelemetry-collector-contrib
that referenced
this pull request
Oct 31, 2024
Separates header processing functions from content processing functions to improve code clarity. This is a follow-up from open-telemetry#35870 (comment).
djaglowski
pushed a commit
that referenced
this pull request
Oct 31, 2024
Separates header processing functions from content processing functions to improve code clarity. This is a follow-up from #35870 (comment).
ArthurSens
pushed a commit
to ArthurSens/opentelemetry-collector-contrib
that referenced
this pull request
Nov 4, 2024
…y#36108) Separates header processing functions from content processing functions to improve code clarity. This is a follow-up from open-telemetry#35870 (comment).
sbylica-splunk
pushed a commit
to sbylica-splunk/opentelemetry-collector-contrib
that referenced
this pull request
Dec 17, 2024
) #### Description Fixes open-telemetry#35869 by refactoring of the `Reader::ReadToEnd` method. This refactors the `Reader::ReadToEnd` method by separating reading the file's header from reading the file's contents. This results in very similar code in `readHeader` and `readContents` methods, which was previously deduplicated at the cost of slightly higher complexity. The bug could be fixed without separating header reading from contents reading, but I hope this separation will make it easier to implement content batching in the Reader (open-telemetry#35455). Content batching was my original motivation for these code changes. I only discovered the problem with record counting when reading the code. #### Link to tracking issue Fixes open-telemetry#35869 #### Testing In the first commit I have added tests that document the erroneous behavior. In the second commit I have fixed the bug and corrected the tests. #### Documentation Added changelog entry.
sbylica-splunk
pushed a commit
to sbylica-splunk/opentelemetry-collector-contrib
that referenced
this pull request
Dec 17, 2024
…y#36108) Separates header processing functions from content processing functions to improve code clarity. This is a follow-up from open-telemetry#35870 (comment).
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.
Description
Fixes #35869 by refactoring of the
Reader::ReadToEndmethod.This refactors the
Reader::ReadToEndmethod by separating reading the file's header from reading the file's contents.This results in very similar code in
readHeaderandreadContentsmethods, which was previously deduplicated at the cost of slightly higher complexity.The bug could be fixed without separating header reading from contents reading, but I hope this separation will make it easier to implement content batching in the Reader (#35455).
Content batching was my original motivation for these code changes.
I only discovered the problem with record counting when reading the code.
Link to tracking issue
Fixes #35869
Testing
In the first commit I have added tests that document the erroneous behavior. In the second commit I have fixed the bug and corrected the tests.
Documentation
Added changelog entry.