mirror of
https://github.com/lancedb/lancedb.git
synced 2026-10-13 23:32:27 +00:00
Brendan Clement
6367f7a0de
Five pages still said a refresh never revisits a filled row and that a changed input needs the column dropped and declared again. Since lancedb#4161 a refresh also recomputes rows whose inputs changed, so the quickstart, the feature-engineering overview, Guarantees, and the SQL REFRESH and UPDATE pages now say that. Retry claims are qualified the same way. A local refresh commits the column once, and a deployment's job commits finished batches. A retry fills what is still empty or stale, but can recompute values that were already written (a refresh whose input record was not saved recomputes next time), so no page promises that a retry costs only the unfinished rows.