Hi! First question 😃
I'd like to know if it's possible to insert commits before some other. Or in other words, to rebase a branch.
My use case : I plan to track data changes in lakefs, creating commits, and besides I have a git repo that has existed for many years about that same data, with commits too. I'd like to import those git repo commits before the lakefs repo commits.
Context : I work for the free software project db.nomics.world (macro economics time series aggregator) that uses git and is switching to object storage, and why not lakefs.
Hi Team,In the architecture documentation lakeFS needs RDB for metadata indexing. In the current implementation it needs PostgreSQL server. AWS aurora serverless V1 supports MySQL and PostgreSQL language. The more powerful aurora serverless V2 only supports (currently) MySQL.Is it possible to extend the RDB support to MySQL as well?Thanks,
Hey LakeFS team, I’m wondering if there is any interest in supporting an SSL certificate env variable for the
utility. I did get a workaround here but as more of our users get interested in the service it would make integration a bit easier for a few reasons. 1. often users at an enterprise don’t have admin rights on their computer to do the fix
2. Makes a similar setup for users on different os
3. Follows similar patterns such as
file for upload command for lakeFS? Let me know if this possible as of now somehow?To add more context, we are using lakeFS in a way that is highly integrated with one’s GitHub repository. As a part of the workflow, one uses the
lakeFS upoad --recursive
command to update the data.
Do you think it makes sense to have an ignore option with the command that can be pointed to an
This is a very high level suggestion and not sure it would work but just my feedback. While I was working with lakefs I felt like I was really missing the git experience of having a current relative position in the tree. For example when I do a
git add .
it's relative to the branch I'm on at that time. Whereas the equivalent command in lakefs that moves data from work space to staging,
lakectl ingest --from --to
doesn't share that same convenience. Its more flexible, but it would be nice to be able to do something like a
such that when I create a new branch it defaults the source to the current branch etc.