flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kirschnick, Johannes" <johannes.kirschn...@tu-berlin.de>
Subject Introduction
Date Thu, 06 Nov 2014 14:17:06 GMT

as have some other fellow colleges as well I would like to introduce myself as well to the
I am a PhD student from Berlin who wants to work with Flink .

As suggested by the getting started guide I had a look at some starter issues and found the
issue about comments in CSV lines

While looking into it I noticed that the current CSV parser does not correctly read escaped
There is of course a debate as to how to escape any value in CSV files, but the common use
is to use " as the escape character

So the following line will not parse

1997,Ford,E350,"Super, ""luxurious"" truck"

I had a look into why that is and if I could propose a fix for it.
Being a novice to the codebase I noticed that the CSV Parser uses the parsers from


So the question I have:

Are these parsers only used for CSV files and thus would introducing the escaping mechanism
just work - or are they used in a lot of other places requiring a special handling in case
of CSV instead.
Thus fixing the escaping would actually mean to break/ fix a lot of other thing?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message