-
Notifications
You must be signed in to change notification settings - Fork 775
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ReadWriteLogRecord#getContext #4888
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
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 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 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 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think(?) the reason that SdkSpan only contains
SpanContext
instead of the fullContext
was to limit memory retention, @jkwatson do you recall anything?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok so there is a subtle difference between holding it in the
SdkReadWriteLogRecord
and holding it in theSdkLogRecordBuilder
such that it can be passed to each log processor as an argumentLogRecordProcessor#onEmit
.If its held in
SdkReadWriteLogRecord
, there's a reference toContext
untilBatchLogRecordProcessor
flushes and converts each log record toLogRecordData
, so the reference sticks around for essentially the shorter of the batch interval or the time it takes to fill the batch queue.If instead the context is held in
SdkLogRecordBuilder
and passed as an argument to eachLogRecordProcessor#onEmit()
, then the reference only has to stick around until the last processor has synchronously returns fromonEmit
. This allows the context to be garbage collected while the corresponding log record is still sitting in theBatchLogRecordProcessor
queue.I think this is a good enough reason to include as an argument to
onEmit()
instead of having a getter onSdkReadWriteLogRecord
.