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
{{ message }}
Repository navigation
Commit 4a10ba3
Browse filesBrowse the repository at this point in the historyBrowse files
[fix](be) Preserve normalizer phrase and scoring behavior
### What problem does this PR solve?
Issue Number: None
Related PR: #69199
Problem Summary: A custom normalizer can split one value into multiple terms, so omitting phrase positions by default can turn indexed phrase queries into scans. A built-in lowercase normalizer emits one term, but its docs-only postings have no frequencies or norms, which caused scoring statistics collection to reject the index. Keep positions for custom normalizers and use unit frequency and document length when scoring built-in lowercase postings without positions or norms.
### Release note
Custom normalizers retain phrase positions by default. Built-in lowercase normalizer indexes keep phrase matching and positive relevance scores with docs-only postings.
### Check List (For Author)
- Test: FE unit tests for normalizer defaults and policy binding; BE unit tests for SNII postings, collection statistics, reader capabilities, and missing norms; C++ format and build hygiene checks.
- Behavior changed: Yes. Custom normalizers retain positions by default, and docs-only lowercase postings remain eligible for scoring.
- Does this need documentation: No
0 commit comments