You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "jin adachi (JIRA)" <ji...@apache.org> on 2011/04/30 13:36:03 UTC

[jira] [Commented] (HIVE-2137) JDBC driver doesn't encode string properly.

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

jin adachi commented on HIVE-2137:
----------------------------------

This patch can set character encoding in the connection string.

For example,
jdbc:hive://10.68.160.236:10000/default
->
jdbc:hive://10.68.160.236:10000/default?characterEncoding=UTF-8

If you set "characterEncoding", string is decoded by character code which was set.
If not set, it's the same as before.


> JDBC driver doesn't encode string properly.
> -------------------------------------------
>
>                 Key: HIVE-2137
>                 URL: https://issues.apache.org/jira/browse/HIVE-2137
>             Project: Hive
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 0.6.0, 0.7.0
>            Reporter: jin adachi
>         Attachments: HiveConnection.patch, HivePreparedStatement.patch, HiveResultSet.patch, HiveStatement.patch, JdbcSessionState.patch
>
>
> JDBC driver decode string by client encoding.
> It ignore server encoding.
> For example,
> server = Linux (utf-8)
> client = Windows (shift-jis : it's japanese charset) 
> It makes character corruption in the client.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira