Database / LanceDB Interview questions
What are tags in LanceDB versioning?
Tags are named, human-readable references to a specific table version — conceptually similar to Git tags — letting you refer to a version by a meaningful name like "pre-migration" or "v2-eval-baseline" instead of remembering an opaque numeric version.
table.tags.create("stable-release", version=12) table.tags.list() table.checkout("stable-release") # checkout by tag name, not number table.tags.delete("stable-release")
Tags support standard CRUD operations — create, list, update, and delete — plus checking a table out directly by tag name rather than needing to know its underlying numeric version, which makes tagged versions far easier to reference correctly across a team or in scripts and documentation.
A meaningful practical benefit is that tagged versions are preserved even when routine cleanup prunes old, untagged versions to reclaim storage: since a tag is a durable reference, LanceDB knows not to delete the underlying version data as long as a tag still points to it, protecting specifically-marked "important" versions from being cleaned up alongside routine intermediate ones.
More Related questions...
