lakeFS is an open-source data version control that transforms your object storage to Git-like repositories..

lakeFS

Hi Team,
I have got a couple of PR merged to <https://github.com/treeverse/airflow-provider-lakeFS> with some important features. Just wanted to check when are we going to create a new release for it. The last one was in Nov 2022.

Hi <@U041V401KRC>, will check and get back to you by tomorrow

Sure, I am also planning to start work on <https://github.com/treeverse/lakeFS/issues/2801>
as suggested by <@U018PQSEPDE> It will improve lakefs a lot.

Hi <@U041V401KRC>, yes :slightly_smiling_face:. Adding a release workflow - if no new issue will be found will publish it by tomorrow.

Ok, please keep me posted and what about the new issue ?

Hey <@U041V401KRC> - please comment on <https://github.com/treeverse/lakeFS/issues/2801|2801> so I could assign it to you

<@U041V401KRC> <https://pypi.org/project/airflow-provider-lakefs/>

<@U018PQSEPDE> I have commented on the github issue. Please assign it to me

Hi <@U041V401KRC>, assigned <https://github.com/treeverse/lakeFS/issues/2801> to you

I see <https://github.com/treeverse/lakeFS/issues/3054|#3054> and <https://github.com/treeverse/lakeFS/issues/5213|#5213> in reference. Do I have to first solve them as well in order to solve this? <@U013V6T7UMC>

The other issues are related, but the specific issue (2801) can be fixed without addressing client version mismatch or trying to identify misconfiguration.

The example in 2801 show that we try to read from lakeFS URI and would like the error to capture the real reason `repository not found` reported by lakeFS rot the client.