opensearch-project / index-management
???? Automate periodic data operations, such as deleting indices at a certain age or performing a rollover at a certain size
Summary
    |
|||
| Main Code: 23,441 LOC (277 files) = KT (96%) + HTTP (2%) + PY (<1%) + YML (<1%) + POLICY (<1%) + JAVA (<1%) Secondary code: Test: 17,041 LOC (128); Generated: 0 LOC (0); Build & Deploy: 604 LOC (5); Other: 3,406 LOC (35); |
|||
| Duplication: 14% | |||
| File Size: 0% long (>1000 LOC), 64% short (<= 200 LOC) | |||
| Unit Size: 0% long (>100 LOC), 58% short (<= 10 LOC) | |||
| Conditional Complexity: 0% complex (McCabe index > 50), 82% simple (McCabe index <= 5) | |||
|
|
Logical Component Decomposition: primary (17 components) | ||
|
|
2 years, 11 months old
|
||
|
|
0% of code updated more than 50 times Also see temporal dependencies for files frequently changed in same commits. |
||
| Goals: Keep the system simple and easy to change (4) | |||
|
Features of interest:
TODOs
36 files |
|||
Latest commit date: 2022-01-21
|
4
commits
(30 days)
3
contributors
(30 days) |
|