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

lakeFS

<@U034GN4BXFZ> can you please add context to <https://github.com/treeverse/lakeFS/issues/7033|this> issue? Trying to understand if this is the tension between APIs that provide separate "open" and "create" routines and APIs that provide a single "open" routine, or something else. (Personally I prefer the former option whenever there is no read+write nice, as then the two return tours are completely disjoint and it is typesafe!)

This was open as part of a discussion I had with <@U0140GK2V8D> regarding the expected functionality (and compatibility with fsspec) and support of a writer object.
As I understand the initial PRD suggested adding write modes to `open`, which was replaced by a `create`  method which is provided with the data.

This design constricts us in scenarios where we want to provide a writer to another process which performs the data fabircation

Some more context: <https://github.com/treeverse/lakeFS/issues/7033#issuecomment-1824316353>

Got it, and obviously useful once you put it like that. Arguably this is most convenient for just about anything. 

Thanks!