[docs] Fix full-text index option defaults and search query examples - #9062
Merged
Merged
Conversation
The primary-key full-text search examples pass the column inside the query JSON, which the native reader rejects with "invalid query: full-text query column 'content' is not configured for this index". The Paimon column is supplied as the procedure/API argument instead. The paimon-full-text README analyzer table, which the primary-key global index docs delegate to, still carries the pre-full-text defaults: stem, remove-stop-words and ascii-folding are true, and ngram.min-gram/max-gram default to 3. Generated-by: Claude Code
Contributor
|
+1 |
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
2 participants
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 #9061
invalid query: full-text query column 'content' is not configured for this index. The column is a procedure/API argument, not a JSON field (full-text.mdxNotes). From [spark][flink][docs] Expose primary-key full-text search #8659; corrected in 5 places.docs/primary-key-table/global-indexdelegates analyzer options to this README, whoseDefaultcolumn still holds pre-full-textTantivy values:stem/remove-stop-words/ascii-foldingsayfalse, 0.1.0 defaults themtrue;ngram.min-gram/max-gramsay2but default to3— a two-characterngramquery from this table returns zero rows. Adds missingjiebarows.Tests
paimon-full-text-index0.1.0, comparing search hits of default vs. explicit-option indexes (macOS aarch64 / JDK 11): min/max-gram,ascii-folding,stem,remove-stop-words, thestop-wordsconstraint andjieba.search-mode.jieba.ordinal-positionmirrorsfull-text.mdx.