Skip to content

bug: Full reload branch merge fails with Concurrent modification on node table #282

@korchoon

Description

@korchoon

What happened

A full reload branch created from main can be loaded and queried successfully, but merging it back into main fails with a Lance/table-version conflict.

Expected: a branch created from main, loaded successfully, and queried successfully should either merge cleanly or fail with a clearer retryable/conflict contract.

Steps to reproduce

  1. Create a branch from main.
  2. Load a generated JSONL seed into that branch.
  3. Query the branch successfully.
  4. Merge the branch back into main.

Approximate workload size:

  • 14.7k nodes
  • 41.6k edges
  • 56k JSONL seed rows
  • 17.7 MB seed
  • 12.3 MB graph after load

Control cases that succeeded on the same graph:

  • empty branch merge
  • tiny delta branch load
  • tiny delta branch merge

PS: Also used for comparison: Ubuntu 24.04.3 LTS on WSL2, kernel 6.6.87.2-microsoft-standard-WSL2, ext4

Version

omnigraph 0.7.0 Installed from the GitHub release binary

Environment

Windows 11 / NT 10.0.22631.4602, x86_64, local filesystem, NTFS

Logs / output

storage: Concurrent modification: table version 6 already exists for node:Chunk

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingneeds-triageAwaiting maintainer triage

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions