CrownChu commented on code in PR #8000:
URL: https://github.com/apache/paimon/pull/8000#discussion_r3557531770
##########
paimon-core/src/main/java/org/apache/paimon/table/source/FullTextScanImpl.java:
##########
@@ -93,7 +94,7 @@ public Plan scan() {
if (globalIndex == null) {
return false;
}
- return textColumnIds.contains(globalIndex.indexFieldId())
+ return !matchedTextColumnIds(globalIndex,
textColumnIds).isEmpty()
&&
supportsFullTextSearch(entry.indexFile().indexType());
Review Comment:
Thanks for pointing this out. This has been addressed in 3b2f57abc4 without
adding a field-level capability API to GlobalIndexerFactory.
We no longer allow a STRING field in es-index to be
keyword-only.`type=keyword` now selects KEYWORD as the primary representation,
while ESIndexOptions automatically adds a `<field>.fulltext` FULLTEXT
multi-field.
The writer indexes the same value into both fields, and
ESIndexGlobalIndexReader routes full-text queries on a KEYWORD-primary field to
`<field>.fulltext`.
Therefore, an es-index file covering a text column is now genuinely capable
of serving full-text search, so the existing index-type-level coverage decision
no longer suppresses a required raw fallback.
--
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]
