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

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

Github user greghogan commented on a diff in the pull request:

    https://github.com/apache/flink/pull/2060#discussion_r78199262
  
    --- Diff: 
flink-core/src/main/java/org/apache/flink/api/common/io/GenericCsvInputFormat.java
 ---
    @@ -314,6 +320,25 @@ protected void setFieldsGeneric(boolean[] 
includedMask, Class<?>[] fieldTypes) {
                this.fieldIncluded = includedMask;
        }
     
    +   /**
    +    * Gets the Charset for the parser.Default is set to UTF-8
    +    *
    +    * @return The charset for the parser.
    +    */
    +   public Charset getCharset() {
    +           return this.charset;
    +   }
    +
    +   /**
    +    * Sets the charset of the parser. Called by subclasses of the parser 
to set the type of charset
    +    * when doing a parse.
    +    *
    +    * @param charset The charset  to set.
    --- End diff --
    
    Double space.


> StringParser not specifying encoding to use
> -------------------------------------------
>
>                 Key: FLINK-3921
>                 URL: https://issues.apache.org/jira/browse/FLINK-3921
>             Project: Flink
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.0.3
>            Reporter: Tatu Saloranta
>            Assignee: Rekha Joshi
>            Priority: Trivial
>
> Class `flink.types.parser.StringParser` has javadocs indicating that contents 
> are expected to be Ascii, similar to `StringValueParser`. That makes sense, 
> but when constructing actual instance, no encoding is specified; on line 66 
> f.ex:
>    this.result = new String(bytes, startPos+1, i - startPos - 2);
> which leads to using whatever default platform encoding is. If contents 
> really are always Ascii (would not count on that as parser is used from CSV 
> reader), not a big deal, but it can lead to the usual Latin-1-VS-UTF-8 issues.
> So I think that encoding should be explicitly specified, whatever is to be 
> used: javadocs claim ascii, so could be "us-ascii", but could well be UTF-8 
> or even ISO-8859-1.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to