This repository has been archived by the owner on Jan 15, 2024. It is now read-only.
feat: store operations in a separate table #23
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
johanneswuerbach
force-pushed
the
operations-table
branch
from
19acde6
to
41ebda3
Compare
johanneswuerbach
changed the title
johanneswuerbach
force-pushed
the
operations-table
branch
from
41ebda3
to
007ef17
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Querying the span table to determine the service names and operations is too slow as the query by default needs to cover the entire retention timeframe.
Use a second table here, which only stores the operations and deduplicates writes for up to 1h to reduce the amount of objects to be scanned.