itaidavid
itaidavid
Currently, there are no benchmarks for graveler. This can make it difficult to identify perfromance regression due to the move to KV. Need to implement benchmarks and run on both...
As described in this [comment](https://github.com/treeverse/lakeFS/pull/3377#discussion_r876714173). The current concurrent flow benchmark checks multiple routines, each uploading a different file (accessing different entries in the tracker table). We want to add a...
Introducing `RepositoryState` - A repository is either `active` - can be used and accessed normally, or it is `deleting` which means it is not accessible for any use, except for...
**DoD** Migration code to port existing data from SQL to KV, and a corresponding test
Though not part of gravler, this functionality is heavily dependent on gravlere and its usage of the underlying store. Having tests for these will add to our coverage and performance...
Backgorund cleaning procedure to collect deleted repositories and correlated entities, as described in #3661 Pending completion of #3714
Upon deletion - move the repository entry to `graveler_deleted` partition and delete from `graveler` Modify creation to allow collection of inital commit and default branch in case of failure. #3661...
Following #3591 and #3646 - we recognized the need for a better error handling mechanizm within `graveler`. #3646 handles the `Repository` section of graveler but similar discovery and implementation should...
Adding `setup.mustache` and configuring `Makefile` to use it and to not delete it. Done to allow to override of the `long_description` field to allow fix of #2344 We should consider...
closes #4121 `lakefs kv get` and `lakefs kv scan` implemented. There is a generic value -> proto -> json converter, that allows each module (auth, graveler, etc.) to associate different...