Skip to content

Fix case-sensitive stop filter causing inconsistent search results #68

@reekitconcept

Description

@reekitconcept

In customer deployments (DLR), searches for TandemX and Tandem-X return different result counts. The root cause is incorrect ordering of the StopFilterFactory in the Solr analysis chain.

When TandemX is tokenized into ["Tandem", "X"], the single-character token X is not removed by the stop filter because it runs before case normalization. Reordering the filters so that case folding happens before stop word filtering ensures consistent behavior regardless of input casing.

The fix and corresponding tests have already been validated in the customer project.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type
No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions