You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2016/04/05 16:43:25 UTC

[jira] [Resolved] (CALCITE-1189) Unit test failure when JVM default charset is not UTF-8

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

Josh Elser resolved CALCITE-1189.
---------------------------------
    Resolution: Fixed

Fixed in https://git1-us-west.apache.org/repos/asf?p=calcite.git;a=commit;h=04c5ff9e8ae0627025406c627f8474913ba863a0

> Unit test failure when JVM default charset is not UTF-8
> -------------------------------------------------------
>
>                 Key: CALCITE-1189
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1189
>             Project: Calcite
>          Issue Type: Bug
>          Components: avatica
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Trivial
>             Fix For: avatica-1.8.0
>
>
> The changes done in CALCITE-1103 (potentially along with the new test for unicode column names in CALCITE-835) was causing failures on some ASF jenkins hosts.
> In TypedValue, when serializing a String in a the Protobuf variant of TypedValue, the resulting bytes were platform dependent, instead of always specifying UTF-8. Protobuf requires UTF-8 bytes for the method we were invoking, and, thus, threw an exception.



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