Planning on releasing a new lakeFS version soon - any objections?

Devs, particularly with write access to github.com/treeverse/lakeFS who can approve: looking for a reviewer for Return token expiry with presigned URLs. aTdHvAaNnKcSe

Planning to release the new lakeFS version really soon. Waiting for some resolution of this question. Any other big blockers?

Regarding this performance bug in Graveler, do you think this kind of solution makes sense? https://github.com/treeverse/lakeFS/pull/6339

@Ariel Shaqed (Scolnicov)@Itai Admi thoughts about how to test this?

Hi all, I'm implementing a logic which uploads objects to S3. As part of the testing I've noticed that when trying to upload an object of size 0 using pre-signed URLs we're getting a 501 Not Implemented from the server (AWS). This does not happen when we upload the object via lakeFS. Is anyone familiar with this issue or a way to work around that?

Planning on releasing a new lakeFS version today. Please let me know if there are any issues we need to wait for.

Quickstart is currently broken, i'm looking into it https://github.com/treeverse/lakeFS/issues/6400 Directly related: I think we should add a check for the quickstart to the release process 🙂

can anyone help with a

lakectl local

problem that I'm hitting? https://github.com/treeverse/lakeFS/issues/6405

another

local

question (kinda following on from my previous one above, but only tangentially): how does one negate the

default true

of this flag?

--pre-sign          Use pre-signed URLs when downloading/uploading data (recommended) (default true)

i.e. if I don't want to

--pre-sign

, is there a

--no-pre-sign

equivalent?

I want to release lakeFS today. Should I wait for anything?

do we publish javadocs in the same way that we do for the python client https://pydocs.lakefs.io/ ?

Plan to release lakeFS - let me know if you want me to wait for your PR or about any blocker

gotta love open source: https://github.com/just-the-docs/just-the-docs/issues/1323 ❤️

Sharing here too this awesome addition: https://github.com/treeverse/lakeFS/discussions/6469

💡 Time for another lakeFS Pro Tip! This time, working with Databricks widgets to dynamically query different branches! 🕒 In this 3 minute demo, you'll learn how to add a branch dropdown to your notebook that lets easily choose different versions of your lakeFS data! 🧙‍♂️ Best part? The Databricks widget API is really simple, so this is only 3 lines of code! ➡️ More info on connecting Spark and Databricks with lakeFS is available the lakeFS docs

Panning on releasing a new lakeFS version. Please let me know if there's something I should wait for

Hi, can someone please take a look at my PR ? https://github.com/treeverse/lakeFS/pull/6440

https://github.com/treeverse/lakeFS/issues/6494 @HT's issue. Some empty user metadata apparently crashes merge. Great first issue if you're looking to understand the overall API flow.

https://github.com/treeverse/lakeFS/issues/6496 Please notice that as part of our plans for lakeFS 1.0.0, we plan to change, deprecate, and remove some of the lakeFS' APIs. You are invited to comment and share your thoughts on the issue above.

Plan to release lakefs version - let me know if you have something pending I need to wait for

Hey, another lakeFS pro-tip! Did you know that lakeFS supports the S3 protocol? You can even use the AWS cli to read/write data from a lakeFS branch! Check out this 3min pro-tip to learn how to do that:

I'm trying to use the OpenAPI code generator option

useSingleRequestParameter

-- it may help Java client version compatibility in #6424. But it seems to be ignored. Has anyone here any experience with it?

That’s cool

FYI: We are releasing a new version of lakeFS. Anyone wants me to wait?

Can anyone review this please? https://github.com/treeverse/charts/pull/203

Plan to release a new lakeFS version today Please let me know if there's anything you want me to wait for

Hello, I am contributor of Openlineage and was just talking to guys present in the Airflow Summit. You're doing amazing thing, especially for the Spark integration. I was wondering if you considered using Openlineage and include some LakeFS specific information within the events (we call it facets). If you did, but then decided to do it different way, I would be happy to know your reasons. The information about dataset versioning you have could be potentially interesting for data catalogs that already integrate with Openlineage like Atlan, Metaphor, etc.

1.0 is coming! ... and we're all excited. You expect 1.0.0 to mean an entire set of promises for compatibility. I have tried to set these out in #6626. I intend to pull it in the next few days and then publish it on #announcements-and-more. So we would love to hear your comments on that PR! You can see the intended rendered document by going to this link. Thanks!

#6646 may be of interest: it replaces the Mockito-based system test for lakeFSFS with one based on MockServer.