public class LegacyIndexFixer extends Object
DefaultIndexRecoveryManager
before Jira 8.10.
We're preserving it here to support post-snapshot-restore fixing in cases where full versioning data isn't available.
Should be removed in 9.0Modifier and Type | Field and Description |
---|---|
static String |
LEGACY_FIXER |
Constructor and Description |
---|
LegacyIndexFixer(SearchProvider searchProvider,
OfBizDelegator delegator,
IssueBatcherFactory issueBatcherFactory,
IssueManager issueManager,
IssueIndexer issueIndexer,
IssueFactory issueFactory,
SearchService searchService) |
Modifier and Type | Method and Description |
---|---|
com.atlassian.core.util.DateUtils.DateRange |
getRangeToRecoverWithoutVersioning() |
void |
reindexIssuesIn(com.atlassian.core.util.DateUtils.DateRange range,
TaskProgressSink taskProgressSink,
boolean conditionalUpdate)
Reindex issues with last updated date within the following range
The range is
fromLatest date in the index
toLatest date in the database (based on the jiraissue table)
The range can actually be negative, indicating there are indexed updates which do not belong and so may need to be removed.
|
public static final String LEGACY_FIXER
public LegacyIndexFixer(SearchProvider searchProvider, OfBizDelegator delegator, IssueBatcherFactory issueBatcherFactory, IssueManager issueManager, IssueIndexer issueIndexer, IssueFactory issueFactory, SearchService searchService)
public void reindexIssuesIn(com.atlassian.core.util.DateUtils.DateRange range, TaskProgressSink taskProgressSink, boolean conditionalUpdate) throws IndexException, SearchException
range
- Date range to recovertaskProgressSink
- A progress sink.conditionalUpdate
- whether or not to perform condition updates when building any documentsIndexException
SearchException
public com.atlassian.core.util.DateUtils.DateRange getRangeToRecoverWithoutVersioning()
Copyright © 2002-2021 Atlassian. All Rights Reserved.