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.
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
[disk-buffering] - Single responsibility for disk exporters #1161
[disk-buffering] - Single responsibility for disk exporters #1161
Changes from 14 commits
8388a4a
694c216
2f388e7
9a29319
36ef54e
101df22
9600235
b7d2171
010c86a
ebd3d66
5a3dc36
0638fa1
357a4f0
4885b11
f4ef495
f3a3228
d26a951
62f41c3
b0a2a6e
42ae1b4
7bd21cf
a134536
43edbf3
93af94a
5061b58
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
The folder name and the serializer must be the same as the ones used in each
ToDiskExporter
impl for it to work properly, so I'm a bit concerned about providing this builder publicly as it seems like it could be easy to misconfigure it. Instead, I would move it (and alsoFromDiskExporter.java
) to the internal package and create public implementations for each signal in this package, similarly to what's done for theToDiskExporter
s.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, I gave that a shot....and it ended up working out and now there's nice parity between the
ToDisk
and theFromDisk
per signal types. Thanks for the idea!Unfortunately, it ended up being a LOT of work to get the tests shored up. For starters, we were several versions behind on the protobufs...and I got us on the latest. The latest, tho, includes the
TraceFlags
as part of the protos, which we hadn't accounted for. There's also asymmetry in several places because theTraceFlags
are not serialized into protobufs for the Exemplars (and maybe also for parent context, I forget).I any case, I had to shim in a bunch of slightly different expected results, which contain the
TraceFlags.getSampled()
which is what we hard-code to on the de-serialization side. I think overall though it probably cleaned up the tests a little and definitely encouraged some reuse.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.
Oh man, I know how painful dealing with these serializations is, especially when it comes to metrics! 😩 thank you for taking the time to update it 🙏
This file was deleted.