Right now the only two error-handling options are:
'''
* "raise" : raise an exception if an error is encountered.
* "skip" : silently skip problematic logs
'''
This means that either one bad log ruins the whole batch or that bad logs don't get reported.
"Robust error handling" is currently targeted for the 0.7 release, but in order to get through "a whole month of logs" this will need to be dealt with sooner (0.4 release).
For now, I propose just a "warn" strategy that prints the error message but keeps chugging.
Right now the only two error-handling options are:
This means that either one bad log ruins the whole batch or that bad logs don't get reported.
"Robust error handling" is currently targeted for the 0.7 release, but in order to get through "a whole month of logs" this will need to be dealt with sooner (0.4 release).
For now, I propose just a "warn" strategy that prints the error message but keeps chugging.