You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Hai Fu Yu (JIRA)" <ji...@apache.org> on 2015/10/14 18:56:06 UTC

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

Hai Fu Yu created PHOENIX-2321:
----------------------------------

             Summary: 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,
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?



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