You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CLIENT_FILTER performance: No recovery/restart record is written in the repository database unless at least one document was stored in the target database
#9
Open
ptitzler opened this issue
Sep 7, 2016
· 0 comments
Recovery/restart records keep track of the last sequence number that was saved in the target database. Assume the source is a huge database and an aggressive filter is defined that eliminates most documents (lets say the first million) from the source. If the service encounters a fatal error before the first recovery record is written, the service restarts processing with sequence number 0 instead of resuming with the last sequence number that didn't pass the filter.
The text was updated successfully, but these errors were encountered:
Recovery/restart records keep track of the last sequence number that was saved in the target database. Assume the source is a huge database and an aggressive filter is defined that eliminates most documents (lets say the first million) from the source. If the service encounters a fatal error before the first recovery record is written, the service restarts processing with sequence number 0 instead of resuming with the last sequence number that didn't pass the filter.
The text was updated successfully, but these errors were encountered: