[ 
https://issues.apache.org/jira/browse/FLINK-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16441175#comment-16441175
 ] 

ASF GitHub Bot commented on FLINK-2435:
---------------------------------------

GitHub user DmitryKober opened a pull request:

    https://github.com/apache/flink/pull/5862

    [FLINK-2435] User-defined types in CsvReader

    [FLINK-2435] Provides the capability of specifying user-defined types in 
Tuple and Row 'containers' while reading from a csv file


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/DmitryKober/flink feature/flink-2435

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/5862.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #5862
    
----
commit 08d76d493c332f624ffae2f1794542968ce47a62
Author: Dmitrii_Kober <dmitrii_kober@...>
Date:   2018-04-17T16:47:50Z

    [FLINK-2435] Provide the capability of specifying user-defined types in 
Tuple and Row 'containers' while reading from a csv file

----


> Add support for custom CSV field parsers
> ----------------------------------------
>
>                 Key: FLINK-2435
>                 URL: https://issues.apache.org/jira/browse/FLINK-2435
>             Project: Flink
>          Issue Type: New Feature
>          Components: DataSet API
>    Affects Versions: 0.10.0
>            Reporter: Fabian Hueske
>            Assignee: Dmitrii Kober
>            Priority: Minor
>             Fix For: 1.0.0
>
>
> The {{CSVInputFormats}} have only {{FieldParsers}} for Java's primitive types 
> (byte, short, int, long, float, double, boolean, String).
> It would be good to add support for CSV field parsers for custom data types 
> which can be registered in a {{CSVReader}}. 
> We could offer two interfaces for field parsers.
> 1. The regular low-level {{FieldParser}} which operates on a byte array and 
> offsets.
> 2. A {{StringFieldParser}} which operates on a String that has been extracted 
> by a {{StringParser}} before. This interface will be easier to implement but 
> less efficient.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to