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
[storage] Remove dependency on archive flag in ES reader #6490
base: main
Are you sure you want to change the base?
[storage] Remove dependency on archive flag in ES reader #6490
Changes from all commits
9d1d999
4f5cad5
af2e9ec
904d3fb
6bc1ebf
0ae679d
c0ea9a2
5659221
52f63fd
c573a66
4976f7b
77d47c0
6b97e7f
bdae29b
2bf4a61
6cf08e8
77ca3c3
686cc8d
b6db77a
20f5f5d
b785631
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.
nit:
getLoggingTimeRangeIndexFn
is a decorator here. Below we use another decoratoraddRemoteReadClusters
, which is also always applied. I recommend movingaddRemoteReadClusters
to be attached here, instead of insidegetTimeRangeIndexFn
, to makegetTimeRangeIndexFn
easier to read.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.
why remove this test? It seems it was counting on different index names, so useful to keep as backwards compatibility guard.
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.
@yurishkuro Its because we don't concatenate the two inside the reader anymore. That logic is handled by the factory. If use_aliases is set and the read alias suffix is set, then we just use that suffix instead of concatenating the two.
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.
could we model that by altering
withArchiveSpanReader
constructor? Specifically to test the condition where the indices become***archive
vs***archive-read
(which I understand happens depending onuse_aliases
being set or not). You don't have any significant changes to the tests for the factory, but that's where the distinction is being captured.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.
@yurishkuro That would just be a difference of changing
ArchiveIndexSuffix
to bearchive
vsarchive-read
because the span reader just respects what is passed in today. This test would need to go into the factory but there isn't a nice way to do that right now because the reader is a concrete type so we can't use a mock to see what is passed into the createSpanReader function. We could make some changes to make the create functions parameters so they can be injected for testing.