You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flavio Pompermaier (JIRA)" <ji...@apache.org> on 2016/05/19 09:52:12 UTC

[jira] [Issue Comment Deleted] (FLINK-3908) FieldParsers error state is not reset correctly to NONE

     [ https://issues.apache.org/jira/browse/FLINK-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flavio Pompermaier updated FLINK-3908:
--------------------------------------
    Comment: was deleted

(was: In order to make FLINK-3908 work properly this issue should be merged)

> FieldParsers error state is not reset correctly to NONE
> -------------------------------------------------------
>
>                 Key: FLINK-3908
>                 URL: https://issues.apache.org/jira/browse/FLINK-3908
>             Project: Flink
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.2
>            Reporter: Flavio Pompermaier
>            Assignee: Flavio Pompermaier
>              Labels: parser
>
> If during the parse of a csv there's a parse error (for example when in a integer column there are non-int values) the errorState is not reset correctly in the next parseField call. A simple fix would be to add as a first statement of the {{parseField()}} function a call to {{setErrorState(ParseErrorState.NONE)}} but it is something that should be handled better (by default) for every subclass of {{FieldParser<T>}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)