airborne12 opened a new pull request, #66872:
URL: https://github.com/apache/doris/pull/66872
### What problem does this PR solve?
Issue Number: None
Related PR: #66052
Problem Summary: FE admitted score() plans for every phrase-enabled SNII
inverted index, but built-in analyzers and ordinary custom analyzers write only
the docs-and-positions tier. They do not persist norms or semantic scoring
metadata, so the BE later failed while opening scoring statistics. This PR
rejects those plans at the selected-index admission gate and admits SNII
scoring only for indexes created with a CommonGrams analyzer, which writes the
scoring tier. Existing V3 behavior is unchanged. The change is query admission
only and does not modify index writes or the storage format.
### Release note
Reject score() queries on SNII indexes that do not persist scoring data
instead of failing later in the BE.
### Check List (For Author)
- Test
- [ ] Regression test
- [x] Unit Test
- [ ] Manual test (add detailed scripts or steps below)
- [ ] No need to test or manual test. Explain why:
- [ ] This is a refactor/code format and no logic has been changed.
- [ ] Previous test can cover this change.
- [ ] No code files have been changed.
- [ ] Other reason
Added end-to-end score pushdown cases for built-in, plain custom, and
CommonGrams SNII analyzers. CheckScoreUsageTest passes all 20 tests. The full
FE build passes with Checkstyle reporting zero violations.
- Behavior changed:
- [ ] No.
- [x] Yes. score() plans for non-scoring SNII indexes now fail during FE
analysis; index writes and the storage format are unchanged.
- Does this need documentation?
- [x] No.
- [ ] Yes.
### Check List (For Reviewer who merge this PR)
- [ ] Confirm the release note
- [ ] Confirm test cases
- [ ] Confirm document
- [ ] Add branch pick label
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
