You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 22, 2019. It is now read-only.
The following string input "name" is functionally equivalent to "name,," even when using a CsvMapper with a schema created from the class. This makes it impossible to ensure the input was purposely truncated or done so in error. This request is to enable functionality that would require the number of field delimiters equal the number of fields defined in the schema.
The text was updated successfully, but these errors were encountered:
cowtowncoder
changed the title
Add support for ensuring all schema fields are represented in readValue input
Fail for missing column values (JsonParser.Feature.FAIL_ON_MISSING_COLUMNS)
Mar 16, 2017
cowtowncoder
changed the title
Fail for missing column values (JsonParser.Feature.FAIL_ON_MISSING_COLUMNS)
Fail for missing column values (CsvParser.Feature.FAIL_ON_MISSING_COLUMNS)
Sep 14, 2017
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
With a bean definition like:
The following string input "name" is functionally equivalent to "name,," even when using a CsvMapper with a schema created from the class. This makes it impossible to ensure the input was purposely truncated or done so in error. This request is to enable functionality that would require the number of field delimiters equal the number of fields defined in the schema.
The text was updated successfully, but these errors were encountered: