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/10/26 16:25:58 UTC

[jira] [Moved] (CALCITE-1469) QueryServer trims Char type padded spaces

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

Josh Elser moved PHOENIX-2322 to CALCITE-1469:
----------------------------------------------

    Affects Version/s:     (was: 4.5.2)
             Workflow: jira  (was: no-reopen-closed, patch-avail)
           Issue Type: Bug  (was: Improvement)
                  Key: CALCITE-1469  (was: PHOENIX-2322)
              Project: Calcite  (was: Phoenix)

> QueryServer trims Char type padded spaces
> -----------------------------------------
>
>                 Key: CALCITE-1469
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1469
>             Project: Calcite
>          Issue Type: Bug
>          Components: avatica
>         Environment: HDP2.3
> Phoenix4.5.2
>            Reporter: Hai Fu Yu
>            Assignee: Josh Elser
>            Priority: Minor
>
> Query server is trimming padded spaces on Char type data and it convert back to fixed length in the client side. 
> This is unexpected to us as common database would likely return fixed-length data in fixed length. Is this intentional for reducing network traffic? It would be great if we could disable auto-trimming on the queryServer.



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