SparkSession conformance rule shouldn't kill whole job if key missing
Open
Conformance
feature
Menas
priority: undecided
under discussion
- Dominant language
- Scala
- Stars
- 33
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
## Background
When SparkSession conformance rule is unable to find a key that the user has inputted, it kills the whole spark conformance job. This is unexpected.
error: `Exception in thread "main" java.util.NoSuchElementException: XXX`
## Feature
Instead of kill off the job, populate errCol with an apropriate message of not finding the key and put null in the column.
Contributor guide
Assessment
This issue has not been assessed yet.