[jira] [Updated] (PHOENIX-2321) Inconsistency toString() between thin client and think client for fixed-length column type

["Hai Fu Yu (JIRA)" <ji...@apache.org>]

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

Hai Fu Yu updated PHOENIX-2321:
-------------------------------
    Description: 
For Char type,
When fetching the resultSet, the think client is trimming spaces before displaying the toString() result on Char type. While the thin client is displaying it as a fixed length string. Which one is expected? and What's the JDBC standard on this?

  was:
For Char type,
the thin client is trimming spaces before it sending over HTTP, and then padding spaces back to display as a fixed length string on the client side.
The think client is receiving fixed length strings for char type, but it trims spaces before displaying resultSet . 
What is the expected behavior on this? What's JDBC standard?


> Inconsistency toString() between thin client and think client for fixed-length column type
> ------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-2321
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2321
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 4.5.2
>         Environment: HDP2.3
>            Reporter: Hai Fu Yu
>            Priority: Minor
>
> For Char type,
> When fetching the resultSet, the think client is trimming spaces before displaying the toString() result on Char type. While the thin client is displaying it as a fixed length string. Which one is expected? and What's the JDBC standard on this?



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