Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support 'untracked' files in lakectl local #8279

Open
Water292 opened this issue Oct 11, 2024 · 3 comments
Open

Support 'untracked' files in lakectl local #8279

Water292 opened this issue Oct 11, 2024 · 3 comments

Comments

@Water292
Copy link

Water292 commented Oct 11, 2024

Hey! I'm using lakectl local , i.e. my local directory has a .lakefs_ref.yaml file in a directory that's linked to a corresponding lakefs repo, branch and commit. Sometimes i want to run lakectl local checkout <path> but I do not want it to overwrite untracked files in that directory. Is this something that is supported / on the roadmap? Similar to how git does not remove untracked paths when doing a git pull. I was able to do this by using lakectl fs download -r <lakefs url> <path> , so just wondering if its possible to implement with lakectl local as well. Thanks in advance!

Slack conversation with @ozkatz - https://lakefs.slack.com/archives/C016726JLJW/p1728595649900559

@tkalir
Copy link
Contributor

tkalir commented Dec 4, 2024

I can work on supporting something like a .lakeignore file to exclude files from local commit\checkout etc, if that's the approach the team wants to go with.

@Water292
Copy link
Author

Water292 commented Dec 5, 2024

Would prefer an option that allows us to blanket ignore all untracked files, and mimics the functionality in lakectl fs download -r <lakefs url> <path> without needing to maintain extra configs. Any particular reason the .lakeignore is preferred given the desired functionality already exists in another form.

@tkalir
Copy link
Contributor

tkalir commented Dec 5, 2024

An ignore file would allow users do local checkout and later local commit without worrying about untracked files, which could be helpful. That said, I can see that your suggestion might be easier to use.
I would wait for someone from the team to weigh in on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants