Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/2901
@fhueske, the `FieldParser`s look to use two methods to parse their fields.
`DoubleParser` uses `FieldParser.nextStringEndPos`, recently added by Timo, to
create a `String` from the byte array which can be easily interpreted with a
non-default `Charset`. The `String` is then parsed by `Double.parseDouble`. The
`IntParser` processes one character at a time ad-hoc.
Should we adopt the first method of converting bytes -> String -> parse for
all `FieldParser`s? This could be done in a separate ticket.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
