Another question. With reference to https://lakefs.slack.com/archives/C016726JLJW/p1760420043187809?thread_ts=1760416389.902419&cid=C016726JLJW above, there isn't a

lakectl mv

command that can handle renaming. I would just like to know, if I simply rename a folder, since

lakefs

will remove and re-upload everything, does it mean that I will also double the storage usage, since

lakefs

tracks changes to my directory?

lakeFS relies on the object stores APIs which don’t have renames unfortunately. It’s one of the cases where it deviates from traditional filesystems. I do want to note that

lakectl fs cp

will copy the data on the storage side, i.e. data will not be uploaded again, but internally in the object store. So to “move” data, you would first have to copy it, then delete it from the source location. But no “re-uploading” is being performed between the lakectl client and the lakeFS server, or between the lakeFS server and the storage layer. I hope this makes sense.

Thanks again for the reply. 1. It seems

lakectl fs cp

is not documented yet in https://docs.lakefs.io/latest/reference/cli/. Experimental command? 2. Surely if I run Surely if I delete objects (with

lakectl fs rm

?) in the repo I'm altering history. In git this would mess up the repository. I suppose this is the same with lakefs?

1. Sorry, I meant

lakectl fs download

2. Nope, that won’t alter history. It will create a delete marker in the uncommitted area of the branch. Previous commits won’t be affected.

Thanks so much. I got it to work now!