Avoid adding values to cache if the current value is the same as adding value

[RushanNanayakkara]

Purpose

When there is a cache miss the value is added to the cache. But in a clustered environment many nodes may simultaneously read the initial value as null and then try to add the value. But at the time of adding the value, the first one to complete adding the value succeeds but other processes proceed to update the value instead of adding the value.

However while adding doesn't invalidate cache, updating does. But since if the new value is the same as the existing one, there's no need to update the value and then invalidate the cache. This behaviour causes unnecessary cache invalidations in clustered environments. This then leads to unnecessary db reads to retrieve the same value again and again.

Changes of this PR performs an equality check between the new value and the value in the cache and skips updating if the values are the same. This avoids unnecessary cache invalidations.

Related Issue/s

• Local Cache Invalidation with Clustering product-is#23518

Dependent on

• Introduce Cache.putIfNoDuplicate function and unit tests carbon-kernel#4281

[jenkins-is-staging]

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/14357216988

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 29 lines in your changes missing coverage. Please review.

Project coverage is 48.11%. Comparing base (5ec9fbf) to head (5ec17d7).
Report is 17 commits behind head on master.

Files with missing lines	Patch %	Lines
...tity/claim/metadata/mgt/cache/LocalClaimCache.java	0.00%	14 Missing ⚠️
...arbon/identity/claim/metadata/mgt/model/Claim.java	0.00%	6 Missing ⚠️
...ity/claim/metadata/mgt/model/AttributeMapping.java	0.00%	5 Missing ⚠️
.../identity/claim/metadata/mgt/model/LocalClaim.java	0.00%	4 Missing ⚠️

❌ Your patch check has failed because the patch coverage (0.00%) is below the target coverage (80.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #6673      +/-   ##
============================================
- Coverage     48.41%   48.11%   -0.30%     
+ Complexity    16512    16177     -335     
============================================
  Files          1833     1833              
  Lines        110201   108772    -1429     
  Branches      20972    20514     -458     
============================================
- Hits          53355    52338    -1017     
+ Misses        49633    49252     -381     
+ Partials       7213     7182      -31     

Flag	Coverage Δ
unit	32.01% <0.00%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jenkins-is-staging]

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/14357216988
Status: success

[jenkins-is-staging]

Approving the pull request based on the successful pr build https://github.com/wso2/product-is/actions/runs/14357216988

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud