Skip to content

branch-4.0: [test](search) Add regression test for wildcard query on variant subcolumns with multi-index #60834#61000

Closed
github-actions[bot] wants to merge 1 commit intobranch-4.0from
auto-pick-60834-branch-4.0
Closed

branch-4.0: [test](search) Add regression test for wildcard query on variant subcolumns with multi-index #60834#61000
github-actions[bot] wants to merge 1 commit intobranch-4.0from
auto-pick-60834-branch-4.0

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Mar 3, 2026

Cherry-picked from #60834

…olumns with multi-index (#60834)

### What problem does this PR solve?

Related PR: #60793

Problem Summary:
Wildcard queries (*, ?) on variant subcolumns with multiple inverted
indexes (one without analyzer, one with standard/lowercase analyzer)
previously returned empty results even when regular TERM search worked
correctly.

This PR adds a regression test
(`test_search_variant_wildcard_custom_analyzer`) to verify the fix from
#60793 with a more realistic scenario matching the HubSpot contacts
table pattern:
- Variant column with dual field_pattern indexes (none +
standard/lowercase)
- firstname/lastname stored in variant subcolumns (`string_8`,
`string_17`)
- 13 test cases covering: TERM baseline,
leading/middle/trailing/single-char wildcards, cross-field AND, and
match-all wildcard
@github-actions github-actions bot requested a review from yiguolei as a code owner March 3, 2026 12:26
@Thearas
Copy link
Contributor

Thearas commented Mar 3, 2026

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@dataroaring dataroaring closed this Mar 3, 2026
@dataroaring dataroaring reopened this Mar 3, 2026
@Thearas
Copy link
Contributor

Thearas commented Mar 3, 2026

run buildall

@yiguolei yiguolei closed this Mar 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants