[SEARCH-2215] FIX Tool Enhancements Created: 27-Apr-20  Updated: 24-Aug-20  Resolved: 24-Aug-20

Status: Done
Project: Search and Discovery
Component/s: None
Affects Version/s: None
Fix Version/s: Search Services 2.0

Type: Epic
Reporter: Martin Stanford Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
Duplicate
Shadow
shadow of MNT-21104 Improving FIX tool in Search Services Open
Epic Name: FIX Tool Enhancements
Release Train: Southall
Delivery Team: Search

 Description   

User Stories

As an administrator, I want tools to limit the number of transactions the FIX tool will attempt to repair, so that I can target critical repairs and avoid overwhelming the system.

As an administrator, I want to understand what a FIX command will do before committing it, so that I can be confident the right content will be indexed.

Acceptance Criteria (Must Have)

  1. It must be possible for an administrator to only repair transactions in a particular time-frame, defined by commit time. E.g. transactions committed after time A and before time B, any transactions committed after time A, or any transactions committed before time A.
  2. It must be possible for an administrator to configure a system wide limit for the number of repair processes that can run at any one time. 

Acceptance Criteria (Should Have)

  1. It must be possible for an administrator to specify the limit on the number of repair processes for a given FIX command. I.e. to override the system wide default.
  2. It must be possible for an administrator to predict the consequences of a given FIX command in terms of number of transactions to be processed and number of nodes to be indexed.
  3. It must be possible for an administrator to predict the consequences of a given FIX command in terms of the actual nodes to be indexed.

"Should have" requirements may be de-scoped, dependent on feasibility, and effort required.

Notes on Implementation

  • It is assumed that FIX capability updates can be implemented using additional parameters for the FIX API call and possibly an additional STOP command. Other approaches can be considered.
  • Predictive requirements - suggested approach is to allow a FIX command to be run in "test mode". This would work through the FIX process with no commits, and return the number of transactions and nodes. A separate report of nodes to be indexed could be generated.
  • Docs ticket required for updates to https://docs.alfresco.com/search-enterprise/concepts/solr-index-fix.html


 Comments   
Comment by Martin Stanford [ 24-Aug-20 ]

Final task is to backport changes to 1.3. This has been moved to the HH customer requests epic.

Generated at Mon Jun 21 20:54:39 BST 2021 using Jira 7.13.15#713015-sha1:7c5ddd2c3e1709974ae9c48c17df8edd3919fe2c.