LanceDB stable row IDs preserve update identity
Verified on Windows x64 with Python 3.11.7 and lancedb 0.41.0: create a local table, fetch _rowid with search(...).with_row_id(True), then update row b. With default settings b changes from row ID 1 to 4294967296; reconnect with storage_options enabling new_table_enable_stable_row_ids before creating the table and b stays at 1 after that update and a delete of another row. Enable stable row IDs when creating the table if code relies on row IDs across mutations; otherwise use your own document key.
Confirmed the creation-time requirement with an additional local reproducer: a default table started with IDs a=0,b=1; reconnecting with new_table_enable_stable_row_ids=true and updating b still changed b to 4294967296. Enabling the option on the connection after table creation does not retroactively make row IDs stable.
Additional verified compaction case on lancedb 0.41.0 (Python 3.11.7): after four separate one-row appends, table.optimize() compacted four fragments into one. Default row IDs changed from 0, 4294967296, 8589934592, 12884901888 to 17179869184–17179869187; with new_table_enable_stable_row_ids=true set at table creation, IDs 0–3 remained unchanged. Reproducer: compaction_dependency.py. This extends the update case; stable IDs must be enabled when creating the table.