Repository navigation
feat(full-text): support full-text search modes for unindexed row ranges - #559
Open
SteNicholas wants to merge 2 commits into
Open
SteNicholas wants to merge 2 commits into
SteNicholas wants to merge 2 commits into
Conversation
SteNicholas
force-pushed
the
PAIMON-406
branch
3 times, most recently
from
November 14, 2026 12:10
9f55edc to
af6138c
Compare
zjw1111
reviewed
Nov 19, 2026
zjw1111
left a comment
Collaborator
There was a problem hiding this comment.
Thanks for adding support for unindexed rows.
Could you add entries to LICENSE for the upstream source included in cmake_modules/full_text.diff and cmake_modules/lucene.diff, following the existing Arrow and ORC patch entries? Please list Apache Paimon Full Text 0.1.0 and Lucene++ 3.0.9 under Apache-2.0, and retain the Lucene++ headers' copyright attribution to Alan Wright (2009–2014).
zjw1111
reviewed
Nov 19, 2026
Use the snapshot's next row ID in full mode and the selected data files' row ranges in detail mode to find gaps in single-field full-text coverage. Plan raw splits only when a selected partition has a full-text index for the column. Keep fast mode index-only. Assign disjoint row ranges to stored and raw splits and pin both to the planning snapshot and schema. Index live, non-null raw text in memory with Tantivy or Lucene++. Apply row filters before ranking and merge stored and raw hits for the final top-k. When scalar search mode is full or detail, evaluate the row filter against data files for uncovered ranges, or for all searched rows if no scalar index can evaluate the predicate. Refs: apache#406
SteNicholas
force-pushed
the
PAIMON-406
branch
from
November 20, 2026 08:25
af6138c to
91a569c
Compare
Member
Author
|
@zjw1111, I added entries to |
This branch has not been deployed
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
Closes #406.
Full-text searches can now find matching rows appended after the last index build.
fastsearches stored shards only. When the selected partitions contain a full-text index for the column,fullfinds gaps below the snapshot’s next row ID anddetailfinds gaps in the selected data files. As in Java Paimon, only single-field indexes count toward coverage.The planner assigns disjoint ranges to stored and raw splits. Workers read the snapshot and schema recorded by the planner. For an explicit snapshot, tag, or timestamp, the planner resolves text and filter columns in the selected snapshot’s schema. A temporary Tantivy or Lucene++ index scores all live, non-null text in the raw ranges. Row filters apply before ranking, and the final top-k combines hits from the temporary index and the stored shards. In
fullanddetailscalar modes, the reader evaluates the filter against data files where scalar indexes lack coverage or cannot evaluate the predicate.Tests
ExecuteLocal()with independent workers that each deserialize one split. It checks both the primary and extra text columns, for top-1 and for all matches.API and Format
RawFullTextSearchSplitexposes the planning snapshot ID, column name, and row ranges. Raw split V1 carries the text field ID and planning schema ID. Stored split V3 adds the planning schema ID, and readers also accept stored V1 and V2. These encodings carry work between C++ workers. Both backends build the temporary index in memory.full-text-index.search-modeandscalar-index.search-modeeach overrideglobal-index.search-modeand default tofast.vector-index.search-modeis reserved for table-level vector search.Documentation
The guide explains how to choose a search mode, how raw text contributes to scores, and how to pin a subsequent data read to the search snapshot, including when a tag retains an expired snapshot. Global index guide
Generative AI tooling
Generated-by: Codex (GPT-6)