[fix](search) Upgrade query type for variant subcolumns with analyzer-based indexes#60782
Merged
airborne12 merged 2 commits intoapache:masterfrom Feb 18, 2026
Merged
Conversation
…-based indexes When FE resolves a variant subcolumn field pattern to an analyzer-based index, the query type must be upgraded from EQUAL_QUERY to MATCH_ANY_QUERY so that select_best_reader picks the FULLTEXT reader instead of STRING_TYPE. Without this, TERM clauses from lucene-mode DSL would open the wrong (untokenized) index directory and tokenized search terms would never match.
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Member
Author
|
run buildall |
TPC-H: Total hot run time: 28816 ms |
TPC-DS: Total hot run time: 184274 ms |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
Contributor
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
zclllyybb
approved these changes
Feb 18, 2026
This file contains hidden or 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
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.
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #60654
Problem Summary:
Follow-up fix for #60654 (SearchDslParser refactoring).
When FE resolves a variant subcolumn field pattern to a specific analyzer-based index and sends its
index_propertiesviaTSearchFieldBinding, the BEFieldReaderResolverwas usingEQUAL_QUERYfor TERM clauses. This causedselect_best_readerto pick theSTRING_TYPEreader (untokenized index directory) instead of theFULLTEXTreader, so tokenized search terms would never match.Root cause: For variant subcolumns with analyzer-based indexes,
EQUAL_QUERYopens the wrong (untokenized) index directory. The query type needs to be upgraded toMATCH_ANY_QUERYsoselect_best_readerpicks the correct FULLTEXT reader.Fix: In
FieldReaderResolver::resolve(), when the field is a variant subcolumn and the FE-providedindex_propertiesindicate an analyzer-based index (should_analyzer()returns true), automatically upgradeEQUAL_QUERYtoMATCH_ANY_QUERYbefore callingselect_best_reader. Also reuse thefb_ititerator to avoid a redundant map lookup.Release note
Fix variant subcolumn search queries to correctly select the FULLTEXT inverted index reader when an analyzer-based index is configured, instead of incorrectly using the untokenized STRING_TYPE reader.
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)