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/12/16 20:06:46 UTC
[jira] [Updated] (PHOENIX-2321) Inconsistency toString() between
thin client and thick client for fixed-length column type
[ https://issues.apache.org/jira/browse/PHOENIX-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hai Fu Yu updated PHOENIX-2321:
-------------------------------
Summary: Inconsistency toString() between thin client and thick client for fixed-length column type (was: Inconsistency toString() between thin client and think client for fixed-length column type)
> Inconsistency toString() between thin client and thick 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)