airborne12 opened a new pull request, #64343:
URL: https://github.com/apache/doris/pull/64343
### What problem does this PR solve?
Issue Number: DORIS-19296
Related PR: None
Problem Summary:
Creating an NGRAM_BF index with multiple columns passed FE validation and
could reach BE tablet creation, where tablet metadata expects each NGRAM_BF
index to bind exactly one column. This rejects invalid multi-column NGRAM_BF
definitions during FE analysis for both inline table indexes and CREATE INDEX.
### Release note
Reject invalid multi-column NGRAM_BF index definitions during DDL analysis.
### Check List (For Author)
- Test <!-- At least one of them must be included. -->
- [ ] Regression test
- Added coverage in
`regression-test/suites/index_p0/test_ngram_bloomfilter_index.groovy` for
inline table index and CREATE INDEX paths. Not run locally because no worktree
Doris cluster was started.
- [x] Unit Test
- `./run-fe-ut.sh --run
org.apache.doris.nereids.trees.plans.commands.IndexDefinitionTest`
- [x] Manual test (add detailed scripts or steps below)
- `./build.sh --fe`
- [ ] 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 <!-- Add your reason? -->
- Behavior changed:
- [ ] No.
- [x] Yes. Invalid multi-column NGRAM_BF index definitions now fail
during FE analysis.
- Does this need documentation?
- [x] No.
- [ ] Yes. <!-- Add document PR link here. eg:
https://github.com/apache/doris-website/pull/1214 -->
### Check List (For Reviewer who merge this PR)
- [ ] Confirm the release note
- [ ] Confirm test cases
- [ ] Confirm document
- [ ] Add branch pick label <!-- Add branch pick label that this PR should
merge into -->
--
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]
