Github user tillrohrmann commented on the pull request: https://github.com/apache/flink/pull/1141#issuecomment-142956414 Yes the reason why I introduced the `CommonCSVInputFormat` instead of unifying it with the `GenericCsvInputFormat` was that we still have the Record API `CsvInputFormat` in the code base. It doesn't need the pojo type information and, thus, I thought that it does not make sense to let it inherit from a class which has these fields. Actually, I would be in favour of removing the Record API's `CsvInputFormat` if possible. Moreover, I would like to more cleanly separate the tuple type `CsvInputFormat` and the pojo type `CsvInputFormat`, because the pojo support was kind of hacked into the original `CsvInputFormat`. Also the way the input format is set up, is imho a little bit clumsy and error-prone (see https://issues.apache.org/jira/browse/FLINK-2692). But this has no high priority.
--- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---