mirror of
https://github.com/lancedb/lancedb.git
synced 2026-11-03 01:06:52 +00:00
Dropping a view unbinds its name and leaves the definition dataset to a cleanup job, so the two are separate events a caller may want to wait on. `drop_view_async` returns the job, the same shape `drop_materialized_view_async` and `drop_function_async` already use: a 202 carries the job id, and a 200 -- nothing bound to the name -- yields an already-finished job. `drop_view` waits on that job before returning, so a caller that does not want to think about cleanup gets the stronger guarantee: when it returns, the definition really is deleted. That differs from `drop_materialized_view` and `drop_function`, which return as soon as the name is unbound; the view API is the newer one and this is the semantic worth having.