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
Error loading exclusion lists exits early without write
Why these changes are being introduced:
If there are any errors loading an exclusion list for a source, e.g.
the file is not accessible or not parseable, we want the transformation process
to fail completely without writes to the TIMDEX dataset.
As-is, we found that all records from the run will write to the dataset but with
action="error". This is good when *some* records fails to understand what they
were and why, but an exclusion list error will fail for *all* records making
this not helpful.
How this addresses that need:
A new custom exception `CriticalError` is introduced that when raised
will break the Transformer.__next__() iterator. In turn, this will
bubble up to the CLI level and terminate the run with a non-zero
process.
This provides a mechanism from within a Transformer's transformation
logic to raise an exception that will break the Transformer.__next__
iteration.
Side effects of this change:
* Failure to load an exclusion list will terminate the run early
and explicitly.
* In the future, catastrophic errors that suggest all records in
the run will fail should also raise this new, custom exception.
Relevant ticket(s):
* https://mitlibraries.atlassian.net/browse/USE-278
0 commit comments