On 08.09.2016, at 14:58, Marshall Schor <[email protected]> wrote: > > The common way to avoid passing context parameters down into the bowels... is > to > use thread local variables, which in this case would not be accessed unless > the > "error" condition occurred, so no performance hit in the normal case.
I'm not worried so much about the performance or the way in which the parameter is passed down. I'm more concerned about what seems to be a non-obvious long-ranging architectural dependency. Hence the preference to handle bad legacy data close to the ingestion point and not close to the heart of the framework. Cheers, -- Richard
