segment replication changes

[sbcd90]

Description

[Describe what this change achieves]

Issues Resolved

#473

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[codecov]

Codecov Report

Merging #529 (344c18f) into main (4339b84) will decrease coverage by 0.07%.
The diff coverage is 6.97%.

@@             Coverage Diff              @@
##               main     #529      +/-   ##
============================================
- Coverage     25.83%   25.77%   -0.07%     
  Complexity      942      942              
============================================
  Files           252      252              
  Lines         10735    10768      +33     
  Branches       1197     1197              
============================================
+ Hits           2773     2775       +2     
- Misses         7715     7746      +31     
  Partials        247      247              

Files Changed	Coverage Δ
...rch/securityanalytics/SecurityAnalyticsPlugin.java	2.43% <0.00%> (-0.07%)	⬇️
...arch/securityanalytics/correlation/JoinEngine.java	0.00% <0.00%> (ø)
...yanalytics/correlation/VectorEmbeddingsEngine.java	0.00% <0.00%> (ø)
...s/resthandler/RestSearchCorrelationRuleAction.java	0.00% <0.00%> (ø)
...nalytics/resthandler/RestSearchDetectorAction.java	0.00% <0.00%> (ø)
...ityanalytics/resthandler/RestSearchRuleAction.java	0.00% <0.00%> (ø)
...ics/transport/TransportCorrelateFindingAction.java	0.00% <0.00%> (ø)
...analytics/transport/TransportDeleteRuleAction.java	0.00% <0.00%> (ø)
...yanalytics/transport/TransportGetAlertsAction.java	0.00% <0.00%> (ø)
...nalytics/transport/TransportGetFindingsAction.java	0.00% <0.00%> (ø)
... and 8 more

[dreamer-89]

Thanks @sbcd90 for this quick change.

Overall changes look good to me, please verify below before merge that for all requests where you added _primary_first preference:

1. Your plugin needs strong reads.
2. You are using IMMEDIATE, WAIT_UNTIL refresh policy for data ingestion. This is because, use of these refresh policies were giving strong reads guarantees before. So, if these are not used, it probably means you don't need strong reads for those search requests.