CommitBuilder::execute(transaction) is per-dataset. There is no public Rust primitive to atomically commit a set of transactions across multiple Lance datasets, even though the namespace specification and the generated REST client already define one.
Any system that maintains an invariant across two or more Lance datasets — e.g., a join-key relationship, a parent/child reference, or a manifest that names which version of each underlying dataset is currently "published" — must coordinate the per-dataset commits at the application layer. The standard workaround is a single coordinating dataset whose atomic commit serves as the linearization point for everything else. That works, but it leaves a window between the per-dataset commits and the coordinator commit during which partial success is observable.
CommitBuilder::execute(transaction)is per-dataset. There is no public Rust primitive to atomically commit a set of transactions across multiple Lance datasets, even though the namespace specification and the generated REST client already define one.Any system that maintains an invariant across two or more Lance datasets — e.g., a join-key relationship, a parent/child reference, or a manifest that names which version of each underlying dataset is currently "published" — must coordinate the per-dataset commits at the application layer. The standard workaround is a single coordinating dataset whose atomic commit serves as the linearization point for everything else. That works, but it leaves a window between the per-dataset commits and the coordinator commit during which partial success is observable.