Manual trigger of re-indexing for specific policy, SR, token #4373
Description
Problem description
Currently indexer runs updates sequentially, i.e. once the previous one completes a new one gets scheduled. Updates can take several hours or longer. This results in the too long of a gap (for some use-cases) between the time when an asset or a document is created and the time when it is visible in the Indexer.
Requirements
- Introduce a new capability into the indexer to trigger manual re-indexing for a specific 'vertical', starting at a specific topic and navigating (only) down the hierarchy for immediate availability of data.
- Develop a UI for users to provide a Topic ID for one of the specific items below as an entry point into the 'vertical':
- Policy
- Standard registry
- Token
- When manual re-indexing is scheduled it must take priority, or the rest should gets postponed until the manually-triggered update is finished.
- The user who triggered the update must be notified when the update is finished.
Definition of done
- Functionality is implemented as per above
- Documentation is updated
Acceptance criteria
- Users are able to update indexer with the specific 'subset' of data within 20 minutes or less.