guy-har

Sure, The expected behavior in both cases (with and without a slash) is to get the OK result and the schema should be created. It won't be exactly like S3,...

I Agree, We must have this functionality. We should be careful with erasing staging though, It can't be restored. Maybe something like requiring some approval in case staging isn't empty...

@kesarwam is this still happening? I checked on master with ACL and With RBAC, wasn't able to reproduce

Created a new account named lakefs-io instead of lakeFS waiting for it to be connected to our billing account in GCS in order to create a public container registry there...

I believe there might still be problems when users do heavy deletes, but I don't think it's that big of an issue. What I do think is a big issue...

@idanovo, I've probably added `compare` by mistake, it really is used only only for committed data Erasing it!

https://lakefs.slack.com/archives/C016726JLJW/p1712066081097729

After checking on some cases, we should handle the case of consecutive ranges on both sides, we wont benefit much from adding only the first. This optimization should be done...

@nopcoder was this fixed as part of upgrading the Azure SDK?