apache / apache/lucene

ComplexPhraseQueryParser with AsciiFoldingFilterFactory (SOLR) [LUCENE-7687]

Open
#8,738 2 comments 0 reactions 0 assignees View on GitHub
affects-version:6.4.1 legacy-jira-priority:Major type:bug
Dominant language
Java
Stars
3.6k
Forks
1.4k
Avg merge
2d 11h
Merged PRs (30d)
88

Description

I modified generic \*_txt-Field type to use AsciiFoldingFilterFactory on query & index.

When quering with

\{!complexphrase}text_txt:"König\*" – there are 0 results

\{!complexphrase}text_txt:"Konig\*" – there are >0 results

\{!complexphrase}text_txt:"König" – there are >0 results (but less than the line above)

and without \{!complexphrase} everything works o.k.

---
Migrated from [LUCENE-7687](https://issues.apache.org/jira/browse/LUCENE-7687) by Jochen Barth, updated Oct 12 2017
Environment:
```
solr-6.4.1 (yes, solr, but I don't know where the bug exactly is)
```

Linked issues:
- [SOLR-11450](https://issues.apache.org/jira/browse/SOLR-11450)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the three complexphrase queries from the issue in Solr 6.4.1, then trace ComplexPhraseQueryParser together with AsciiFoldingFilterFactory to identify where accented wildcard terms diverge. Done means the accented and unaccented wildcard phrase queries return equivalent expected matches while preserving the existing non-complexphrase behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
search
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.