Skip to content

To ignore non configurable attributes from the cache quality measurement - description updated #1520

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kmohr-soprasteria merged 1 commit into from
Jan 5, 2026
Merged

To ignore non configurable attributes from the cache quality measurement - description updated #1520

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion spec/additionalDescription/CyclicCacheQualityMeasurementProcess.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,6 @@ The module performs a structured tree-based comparison:
- Attribute-level differences: mismatches in leaf-node values.
- Attribute-class mismatches: data classes present in the live structure but absent in the cache or vice versa (missing classes) .


### Scoring model
Each type of difference is assigned a configurable weight:

Expand All @@ -65,6 +64,12 @@ Each type of difference is assigned a configurable weight:

A total weighted score is computed per device and used to quantify the extent of divergence.

### Ignored attributes

Since most of the non configurable attributes do not contribute to cache quality measurement, certain attributes are to be ignored during comparison.
These attributes are listed in #1486.
Note: this change has already been implemented with 2.0.1_impl, without a profile instance being available in the spec. This profile instance will be added with a future release.

### Output

Each completed comparison will add a new entry into ElasticSearch. The following example shows such an entry:
Expand Down
Loading