opensearch-project / data-prepper
Features of Interest
Aspects in the source code identified through RegEx patterns.
Intro
Features of interest are any aspects of a software system that can be identified through patterns in code.
Features of interest provide you with a way to focus your attention on relevant parts of the codebase.
Typical examples include, security, TODOs, logging.
A feature of interest may be present in multiple files. Any source code file may be in zero or multiple features of interest.
Overview
GENERAL
TODOs
3,260 LOC (24%)
34 files
|
found text
|
found text per file
1 GENERAL Concerns
The "general" group contains
2
concerns.
TODOs
Unclassified
general
1.1 TODOs
3,260 LOC (24%)
34 files
|
found text
|
found text per file
The following criteria are used to filter files:
files with any line of content like "
.*(TODO|FIXME)( |:| ).*
".
34
files match defined criteria (
3,260
lines of code,
24.4%
vs. main code):
32
*.java files (
3,209
lines of code)
2
*.yml files (
51
lines of code)
49
lines match the content pattern.
details...
per component - primary logical decomposition
data-prepper-core/src
in 7 files, 718 LOC (34%)
data-prepper-api/src
in 2 files, 35 LOC (2%)
data-prepper-plugins/opensearch
in 6 files, 725 LOC (44%)
data-prepper-plugins/peer-forwarder
in 2 files, 241 LOC (24%)
data-prepper-plugins/common
in 5 files, 278 LOC (30%)
e2e-test/trace
in 3 files, 293 LOC (48%)
data-prepper-plugins/service-map-stateful
in 1 file 266 LOC (60%)
data-prepper-plugins/http-source
in 5 files, 272 LOC (62%)
research/zipkin-opensearch-to-otel
in 1 file 149 LOC (49%)
data-prepper-plugins/otel-trace-group-prepper
in 1 file 171 LOC (70%)
data-prepper-plugins/mapdb-prepper-state
in 1 file 112 LOC (100%)