Parsing leniency differs between EnceladusDateTimeParser and Spark #707
Labels
bug
Something isn't working
priority: medium
Important but not urgent
Standardization
Standardization Job affected
Describe the bug
During #466/ #679 implementation I noticed some skipped test were actually failing. Upon investigation it turns out Spark and
EnceladusDateTimeParser
have different setup for the pattern parsing leniency.That causes different behavior of both, end can lead to unexpected Standardization failures
To Reproduce
Struct field with
pattern
= "dd-MM-YYYY" anddefault
= "2015-01-01" passes validation but fails in Spark/StandardizationExpected behaviour
Spark and
EnceladusDateTimeParser
behave similarly in string parsing, validation is reliable.The text was updated successfully, but these errors were encountered: