Accessing the secondary index may sometimes fail due to a temporary
issue with the index. In this case we want to retry scanning for changes
to auto-close.
This is especially important because the push succeeds even if
auto-closing changes fails. If this happens the changes are in an
inconsistent state, they are still open but the changes were actually
already merged into the target branch. Since the push succeeded the user
cannot retry the operation to get the auto-closing done.
Temporary issues with accessing the index are not common with Lucene but
at Google where we have a custom index implementation we have such
short-term failures frequently.
Using RetryHelper to retry scanning for changes to auto-close is not
optimal because RetryHelper is designed for retrying updates to NoteDb
(e.g. the RetryHelper configuration and the exception handling is
specific for NoteDb updates).
Change-Id: I8c16487780f40d99b9f843ac5bac4c35776e726f
Signed-off-by: Edwin Kempin <ekempin@google.com>
ced85fc9d2