Implement Elasticsearch/Clickhouse source resolver #19
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
pivovarit
force-pushed
the
source-resolver
branch
5 times, most recently
from
13df5f1 to
0c4eae9
Compare
jakozaur
approved these changes
May 2, 2024
pivovarit
added a commit
that referenced
this pull request
May 6, 2024
In this change, I integrate the source resolver with the search logic and use it to determine the strategy. This change is supposed to be neutral, so the original strategy is preserved, but all the search logic moved into a loop, which makes it multiple-table friendly. Depends on: - #19
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.
Implemented a component responsible for identifying which index names behind an index pattern exist and from which source should be queried.
I will integrate it into multi-index search in the next change.