apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yogi Devendra (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (APEXMALHAR-2198) ReaderContext should handle different encodings for String
Date Tue, 23 Aug 2016 15:18:20 GMT

     [ https://issues.apache.org/jira/browse/APEXMALHAR-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yogi Devendra updated APEXMALHAR-2198:
--------------------------------------
    Assignee:     (was: Yogi Devendra)

> ReaderContext should handle different encodings for String
> ----------------------------------------------------------
>
>                 Key: APEXMALHAR-2198
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2198
>             Project: Apache Apex Malhar
>          Issue Type: Improvement
>            Reporter: Yogi Devendra
>
> As per the discussion on this link:
> https://github.com/apache/apex-malhar/pull/372#discussion_r75885695
> Gaurav wrote:
> This is lossy write to tmpBuilder using ByteArrayOutputStream.write(int). byte[] to String
conversion (line 193) is based on default encoding. In case default encoding where multiple
bytes are required to store chars, this will lead to lose of data...
> After looking at the code little more, I also found that code can be simplified a lot
and we can get rid of tmpBuilder and emptyBuilder



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

Mime
View raw message