thswlsqls opened a new issue, #9061: URL: https://github.com/apache/paimon/issues/9061
**Search before asking** - [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar. **Paimon version** master @ a5e87ebf6 (2.1-SNAPSHOT), `paimon-full-text-index` 0.1.0 **Compute Engine** Flink / Spark (also reproducible through the Java API) **Minimal reproduce step** 1. Create a primary-key table with a full-text global index on `content`. 2. Copy the documented example from `docs/docs/primary-key-table/global-index.mdx` (lines 417, 434, 483), `docs/docs/flink/procedures.md` (line 1167) or `paimon-full-text/README.md` (line 132): ```sql CALL sys.full_text_search(`table` => 'default.items', `column` => 'content', query => '{"match":{"column":"content","terms":"paimon lake"}}', top_k => 10); ``` **What doesn't meet your expectations?** The search should return rows. It fails with `RuntimeException: invalid query: full-text query column 'content' is not configured for this index`. The native index has a single text field; the Paimon column is passed as the procedure/API argument, as `docs/docs/multimodal-table/global-index/full-text.mdx` "Notes" states. The examples were introduced by #8659; the working form is `'{"match":{"query":"paimon lake"}}'`. **Anything else?** The `paimon-full-text/README.md` analyzer table, which `docs/primary-key-table/global-index` delegates to, still lists pre-`full-text` defaults: `stem`, `remove-stop-words`, `ascii-folding` as `false` (actually `true`) and `ngram.min-gram`/`max-gram` as `2` (actually `3`). **Are you willing to submit a PR?** - [x] I'm willing to submit a PR! -- 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]
