lance-format / lance-format/lance

Use original base paths when writing to a branch

Open
#7,785 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

feature
Dominant language
Rust
Stars
7.1k
Forks
852
Avg merge
3d 18h
Merged PRs (30d)
272

Description

The overall flow we'd like to be able to do is:

  1. Make new experimental branch
  2. Write some data files to that branch
  3. Add those data files to the main branch
  4. Delete the experimental branch

Right now, data files written in a branch seem to go into a directory under that branch. Deleting the branch will delete those data files.

It's not clear why the branch needs it's own data file directory (similar question with deletion files).

Can we have an option to always use the normal base path for data files? And is there a reason not to make that the default behavior?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how branch writes and deletion files choose their data-file directory, then compare that behavior with the normal base path. Determine whether an option or default change can preserve files after the experimental branch is deleted, and verify the requested experimental-branch workflow with relevant tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.