leaves12138 commented on code in PR #8818:
URL: https://github.com/apache/paimon/pull/8818#discussion_r3687814112


##########
docs/docs/multimodal-table/global-index.mdx:
##########
@@ -399,7 +399,8 @@ These table options affect global index build and read 
behavior:
 | `vector-index.search-mode` | `fast` | Search mode for vector queries. |
 | `full-text-index.search-mode` | `fast` | Search mode for full-text queries. |
 | `global-index.external-path` | Not set | Root directory for global index 
files. If not set, files are stored under the table index directory. |
-| `global-index.column-update-action` | `THROW_ERROR` | Action for updates to 
indexed columns. `THROW_ERROR` rejects the update, `DROP_PARTITION_INDEX` drops 
affected partition indexes, and `IGNORE` keeps existing index files unchanged. 
Use `IGNORE` only when a stale index is acceptable; for example, a vector 
updated from `NULL` to a value remains invisible until the index is rebuilt. |
+| `global-index.column-update-action` | `THROW_ERROR` | Action for updates to 
indexed columns. `THROW_ERROR` rejects the update, `DROP_PARTITION_INDEX` drops 
affected partition indexes, and `IGNORE` keeps existing index files unchanged 
until the index is rebuilt. Set this to `IGNORE` together with 
`global-index.detect-datafile-change=true` to refresh affected row ranges 
during the next incremental index build. |
+| `global-index.detect-datafile-change` | `false` | Whether incremental global 
index builds scan active data manifests to detect changes in already indexed 
row ranges. Enable this together with 
`global-index.column-update-action=IGNORE` to rebuild affected ranges. Index 
files created before this metadata was introduced are not refreshed 
automatically. |

Review Comment:
   OK~



-- 
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]

Reply via email to