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

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

GitHub user fhueske opened a pull request:

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

    [FLINK-5771] [core] Fix multi-char delimiter detection in 
DelimitedInputFormat

    Fix multi-char delimiter detection in DelimitedInputFormat.
    
    - Add a test case to validate correct delimiter detection.
    - Remove a couple of try-catch blocks from existing tests.


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

    $ git pull https://github.com/fhueske/flink delIFFix

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

    https://github.com/apache/flink/pull/3316.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 #3316
    
----
commit d1edaec0310bb10948d8080c1fffde7e716e0d7f
Author: Fabian Hueske <[email protected]>
Date:   2017-02-14T21:02:26Z

    [FLINK-5771] [core] Fix multi-char delimiter detection in 
DelimitedInputFormat.
    
    - Add a test case to validate correct delimiter detection.
    - Remove a couple of try-catch blocks from existing tests.

----


> DelimitedInputFormat does not correctly handle multi-byte delimiters
> --------------------------------------------------------------------
>
>                 Key: FLINK-5771
>                 URL: https://issues.apache.org/jira/browse/FLINK-5771
>             Project: Flink
>          Issue Type: Bug
>          Components: filesystem-connector
>    Affects Versions: 1.2.0
>            Reporter: Colin Breame
>            Assignee: Fabian Hueske
>         Attachments: Test.java, test.txt
>
>
> The DelimitedInputFormat does not correctly handle multi-byte delimiters.
> The reader sometimes misses a delimiter if it is preceded by the first byte 
> from the delimiter.  This results in two records (or more) being returned 
> from a single call to nextRecord.
> See attached test case.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to