Hi all! I recently observed a weird behavior reg...
# help
c
Hi all! I recently observed a weird behavior regarding upload object process. I uploaded a bunch of objects using lakectl, none of them thrown a error so I supposed everything was okay. This morning I retrieve some of that data and 2% of the data was corrupted (they were binary objects instead of csv). However the size of the file is the correct one. Any idea of what happened?? 😞 version: 1.29.0
😱 1
a
lakeFS does very little with the data of an object, it manages metadata (name, size, versions, etc.). This explains why the objects have the right size, despite you seeing the wrong contents. How do you know that they are "binary"? What "corruption" are you seeing? Asking because hopefully the data are there and it's metadata issue.
c
We are trying to know if its a problem where LakeFS its installed or the own LakeFS. We know that is "corrupted" because the file should be a csv and when you try to open it using VSCode it says that its a binary file.
a
Let's try an experiment: Can you try to open it in some other form? CSV files are really just text, so a text editor (even notepad) might be able to open something. Or download the file, rename it to have a .txt extension, and try to open that.
c
Yes, they are just... characters haha
Screenshot 2025-11-24 at 16.26.31.png,Screenshot 2025-11-24 at 16.26.46.png
Well if you zoom in a bit it says NULL
a
I'm sorry, I have poor vision and cannot read jpegs of text. If you can copy a block of text and attach it here, that would be helpful.
There is nothing in lakeFS to generate a string "NULL". Do you by chance know how you generated and uploaded these files all those months ago?
Also, from the red background it seems like it's not opened in a text editor. If the files are not proprietary or large, could you DM me one as an attachment please?