Don't call Pipeline::valid()
recursively when a row is discarded
#119
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, when a row is discarded (e.g. by the Transformer), the Pipeline::valid function manually increments the current key, then calls itself recursively. When discarding many rows, this not only leads to extremely deep call stacks, it also seems to cause execution time to grow linearly as extraction loop progresses.
By changing the discarded behaviour to a simple
break;
statement the valid function will simply returntrue
, bypassing subsequent steps (e.g. the Loader) and progressing on to the next row without recursion.