You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Fabian Hueske (JIRA)" <ji...@apache.org> on 2017/12/29 21:26:00 UTC

[jira] [Created] (FLINK-8331) FieldParsers do not correctly set EMPT_COLUMN error state

Fabian Hueske created FLINK-8331:
------------------------------------

             Summary: FieldParsers do not correctly set EMPT_COLUMN error state
                 Key: FLINK-8331
                 URL: https://issues.apache.org/jira/browse/FLINK-8331
             Project: Flink
          Issue Type: Bug
          Components: Core
    Affects Versions: 1.5.0, 1.4.1
            Reporter: Fabian Hueske


Some {{FieldParser}} do not correctly set the EMPTY_COLUMN error state if a field is empty.
Instead, they try to parse the field value from an empty String which fails, e.g., in case of the {{DoubleParser}} with a {{NumberFormatException}}.

The {{RowCsvInputFormat}} has a flag to interpret empty fields as {{null}} values. The implementation requires that all {{FieldParser}} correctly return the EMPTY_COLUMN error state in case of an empty field.

Affected {{FieldParser}}:

- BigDecParser
- BigIntParser
- DoubleParser
- FloatParser
- SqlDateParser
- SqlTimeParser
- SqlTimestampParser



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)