Repository navigation
[core] Decide full-text row filters from data when no scalar index can evaluate them - #10381
Merged
JingsongLi merged 1 commit intoOct 5, 2026
Conversation
…n evaluate them When every scalar global index covering the filter columns declines the predicate at runtime (for example an FM index on an equality filter), DataEvolutionFullTextRead#matchedRows dropped the index-covered rows, so full-text search with a row filter returned nothing in search mode full or detail. Decide those rows by reading their filter columns, like rows whose filter columns have no index. Fast mode is unchanged. Generated-by: Claude Code
Contributor
|
+1 |
XiaoHongbo-Hope
pushed a commit
that referenced
this pull request
Oct 8, 2026
…n evaluate them (#10381)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
fix #10380
=),DataEvolutionFullTextRead#matchedRowsdropped the covered rows, sofull/detailreturned nothing.full/detailthese rows are now decided by reading their filter columns, as full-text.mdx documents for unindexed rows and fm.mdx promises for declined predicates.DataEvolutionGlobalIndexScanner([core] Support composite BTree equality queries for data evolution tables #10339).fastis unchanged; extra reads happen only in opt-infull/detailand only for declined rows, the same cost as an unindexed column.Tests
FullTextSearchBuilderTest#testFullTextSearchReadsFilterColumnsWhenScalarIndexDeclinesFilter(fast/full/detail). Without the fix,full/detailfail (expected[5], got[]); with it, 3/3 pass.mvn -pl paimon-core clean install(JDK 11): all tests pass, includingFullTextSearchBuilderTest57/57;PostgresqlCatalogTestwas skipped (needs Docker).