CMR-11155: Version Control Index Set - Part 1#2455
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #2455 +/- ##
==========================================
- Coverage 58.20% 58.15% -0.06%
==========================================
Files 1069 1070 +1
Lines 74278 74381 +103
Branches 2166 2164 -2
==========================================
+ Hits 43233 43254 +21
- Misses 29028 29106 +78
- Partials 2017 2021 +4 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
I first glance I am wondering why you chose the path to "create" a new concept, instead of just creating a database table with get/set functions for it for the index set - which I thought we already had - maybe I am remembering the redis cache. |
|
In the beginning, it was easier to treat index-set like a concept and borrow the metadata-db funcs to keep revisions, delete old revs, updates/deletes, etc. I wanted to keep all database interactions under the same pattern. Index-set table did not exist prior to this change. |
Overview
What is the objective?
To allow for disaster recovery and keeping track of historical changes of index-set.
What are the changes?
This is PART 1 of 2 PRs to reduce PR size. This PR mainly introduces helper funcs that will be needed for the major changes in PART 2.
What areas of the application does this impact?
Indexer
Required Checklist
Additional Checklist