I’ve just started testing out the event recovery. Got it up and running, and it appears to be recovering the bad rows, which is great.
But what’s strange is that I’m also seeing it pick up good rows that were previously processed - any idea what could be causing this?
It seems like we have a
part-id.txt file in our ‘bad’ rows that might also include good rows as well as bad in the
line, and the errors it encountered at the end of the file. We don’t store each event as a separate item in S3.
Does this seem like an error in the recovery process not being able to filter out the errors, or is the way we’re storing events the issue?