XYZhan eb9459e3be refactor: replace a spec by unsetting it, not by setting over it ...

A spec records how the generations already written were homed, and only its
maintained index set could move. Accepting that one repeat means a caller who
passes a different sharding — not knowing a spec is installed — gets a success
that changed nothing of what they asked for.

`set_lsm_write_spec` refuses while a spec is installed, and the refusal names
`unset_lsm_write_spec`. Unset drains the open writer first, so the rows it held
reach base before the new spec installs.

The default intent still reaches a live writer when an index is created, which
is the case that needed no spec change at all.

2026-10-01 16:57:04 -04:00

..

lancedb

feat(functions): address Functions by namespace path (#4341)

2026-09-29 14:07:14 -07:00

tests

refactor: replace a spec by unsetting it, not by setting over it

2026-10-01 16:57:04 -04:00

type_tests

fix(python): expose inline types to downstream checkers (#3817)

2026-08-07 17:31:42 +08:00