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 b24f0ea
Browse filesBrowse the repository at this point in the historyBrowse files
[feat](inverted-index) Backport IK custom analyzers to branch-4.1
### What problem does this PR solve?
Related PR: #67918
Problem Summary:
Custom inverted-index analyzers on branch-4.1 cannot use IK smart or max-word
tokenization. Backport the tokenizer factories, source-byte offset tracking,
analyzer identities, and saved-policy resolution from the merged PR. Adapt the
FE and BE changes to the 4.1 layout and interfaces while preserving its NGram
validation limits.
### Release note
Custom inverted-index analyzers support ik_smart and ik_max_word tokenizers.
### Check List (For Author)
- Test
- [x] Regression test: the three added analyzer suites passed on an isolated ASAN cluster.
- [x] Unit Test: 437 BE tests, 34 PolicyValidatorTests, and 62 AnalyzerIdentityBuilderTest tests passed.
- [x] ASAN BE and BE Java extensions built. The local BE build used an ignored compatibility shim for unavailable Lance symbols; Lance behavior was not tested.
- [x] FE build passed, including Checkstyle.
- [x] Clang-format 16 checked all 79 changed C++ files; clang-tidy found no changed-line warnings after target-specific fixes.
- Behavior changed:
- [x] Yes. Custom IK tokenizers, analyzer selection, and source offsets work across DDL, indexing, and MATCH queries.
- Does this need documentation?
- [x] No. Existing custom-analyzer syntax is reused.
(cherry picked from commit ef72b93)
Conflicts:
- FE analyzer code is in fe-core on branch-4.1, and the BE reader and test APIs differ.
- branch-4.1 lacks max_ngram_diff, so its existing NGram bounds remain in use.
0 commit comments