airborne12 opened a new pull request, #66876:
URL: https://github.com/apache/doris/pull/66876
### What problem does this PR solve?
Issue Number: None
Related PR: #66052
Problem Summary:
SNII keyed its result cache and query single-flight by the raw query before
analysis. Plain custom-analyzer segments do not persist an immutable analyzer
identity, so two live generations under the same analyzer name could tokenize
identical raw bytes differently while reusing the first generation bitmap. Gate
pre-analysis sharing with the existing analyzer-context capability. Providers
without a segment-fixed identity now analyze independently, while raw pattern
queries and contexts with complete immutable CommonGrams identity retain
sharing.
### Release note
Prevent SNII queries from reusing cached results produced by a different
custom analyzer generation.
### 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
Tests run:
-
SniiIndexReaderCountFallback.CustomAnalyzerProviderGenerationsDoNotShareRawQueryCache
-
SniiIndexReaderCountFallback.CustomAnalyzerWithoutImmutableIdentityBypassesRawQueryCache
- SniiIndexReaderCountFallback.*
- ./build.sh --be -j 192
- Behavior changed:
- [ ] No.
- [x] Yes. SNII bypasses pre-analysis result sharing when analyzer
semantics are not fixed by immutable segment identity.
- 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]
