Add unit test to check infinite looping due to ingest parse failure #243
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.
Adds a unit test in FilteringCloseableRowIteratorTest which checks whether there's an infinite looping when an exception raises from ingest parse failures.
Description
A bug related to iterator looping infinitely and thereby halting ingestion was fixed in #222 . Corresponding unit test is being added here to prevent ingestion from halting when a parse exception occurs beyond the set threshold.
Fixed the bug ...
Renamed the class ...
Added a forbidden-apis entry ...
Release note
For tips about how to write a good release note, see Release notes.
Key changed/added classes in this PR
MyFoo
OurBar
TheirBaz
This PR has: