Enterprise only
A LanceDB extension with no DataFusion equivalent.
full = true forces a complete rebuild
even when the sources are unchanged; the default, false, refreshes
incrementally when supported and rebuilds otherwise.
CASCADE is not accepted by the SQL implementation described here,
regardless of what a local SDK’s refresh() method accepts — do not
assume the two option sets match.Resource budgets
Set budgets for one refresh execution:cpu_millis is CPU capacity in millicores (1000 = one core), not CPU time.
memory_bytes caps memory in bytes. gpu_count caps concurrent GPUs for the
refresh. These are aggregate caps across its SQL execution and Function
processes; they are not multiplied by the number of Functions in the query.
CPU or memory requires all three budget fields. CPU and memory must be positive;
gpu_count = 0 is allowed for CPU-only views. A GPU budget alone is also accepted.
A cap does not reserve all of its GPUs or increase refresh parallelism. Current
MV refreshes use at most one GPU, shared by their GPU Function calls.
gpu_class selects an operator-configured class for this execution, leaving the
Function registration and saved MV placement unchanged. Use SHOW GPU CLASSES
to discover configured classes. Omitted budgets and class preserve defaults.
Options can be combined with full = true.
This requires an Enterprise server and an isolated execution backend that can
enforce resource budgets. Unsupported backends reject constrained refreshes.
Older servers reject the new options. Saved defaults and automatic refresh
configuration are unchanged.
Watching a refresh
A refresh submits work that outlives the call. Track it withSHOW JOBS, and diagnose failures with
SHOW ERRORS. For per-split progress, worker fleet
detail, and a DESCRIBE JOB example, see Watching a refresh.
See also
Materialized View
Creating the view this refreshes.
Refresh a materialized view
The same operation from the SDKs, and automatic refresh.
REFRESH COLUMN
Filling a computed column, instead of a view.