I have a question about branching:
Say we want to use lakeFS on our production system. Everyday we load new data in batch jobs (or streaming).
What is the best pattern to make this possible using lakeFS? every batch load is a commit on main branch, or a feature branch per pipeline or ...?
Basically I just want to know how a 'normal' production scenario would look like using lakeFS.
6 months ago
hi, if i create a lakefs branch (say off of master, or perhaps another branch or tag), and then, in that branch, without making any changes or commits, i delete the data - will this affect the data in the original branch/tag that my new branch was based on? i would imagine it should not, but wanted to confirm - thanks