You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #3734, we introduced the multi indexes search feature.
With one limitation: it works only if the resolved query AST is the same on all indexes. And query AST can be different when indexes have different search default values.
There is a use case where searching on indexes with different default values is beneficial. For example, if you want to search on one index containing logs, another containing transactions, etc. Searching for a specific ID in all the indexes is impossible currently (except if you are searching in a JSON field). But if we allow default_fields in the different indexes will make the search experience possible.
Possible Solution
It's easy to keep around one query AST per index and attach the right query AST to the leaf requests.
The main issue comes from how we list the relevant splits for a given query. In the current code base, we call list_splitswith a ListSplitsQuery argument. Everything works well except for the TagAstFilter as it accepts only one tag AST. However, different default values between indexes will lead to different TagAstFilter.
To avoid that, we could fire multiple list_splits for indexes with different TagAstFilter, which will solve our problem.
The text was updated successfully, but these errors were encountered:
In #3734, we introduced the multi indexes search feature.
With one limitation: it works only if the resolved query AST is the same on all indexes. And query AST can be different when indexes have different search default values.
There is a use case where searching on indexes with different default values is beneficial. For example, if you want to search on one index containing logs, another containing transactions, etc. Searching for a specific ID in all the indexes is impossible currently (except if you are searching in a JSON field). But if we allow
default_fields
in the different indexes will make the search experience possible.Possible Solution
It's easy to keep around one query AST per index and attach the right query AST to the leaf requests.
The main issue comes from how we list the relevant splits for a given query. In the current code base, we call
list_splits
with aListSplitsQuery
argument. Everything works well except for theTagAstFilter
as it accepts only one tag AST. However, different default values between indexes will lead to differentTagAstFilter
.To avoid that, we could fire multiple
list_splits
for indexes with differentTagAstFilter,
which will solve our problem.The text was updated successfully, but these errors were encountered: