You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Jinchul Kim (JIRA)" <ji...@apache.org> on 2017/12/14 00:16:00 UTC

[jira] [Resolved] (IMPALA-2640) Capitalization lost from statement name when impala-shell echoes the query

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

Jinchul Kim resolved IMPALA-2640.
---------------------------------
    Resolution: Duplicate

> Capitalization lost from statement name when impala-shell echoes the query
> --------------------------------------------------------------------------
>
>                 Key: IMPALA-2640
>                 URL: https://issues.apache.org/jira/browse/IMPALA-2640
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Clients
>    Affects Versions: Impala 2.3.0
>            Reporter: John Russell
>            Assignee: Jinchul Kim
>            Priority: Trivial
>              Labels: ramp-up, usability
>
> I don't know how long this has been going on but I just noticed it recently.
> By default, impala-shell echoes the query after you type it, preserving the same capitalization the user entered. Except that the first word (i.e. the statement name) gets turned into all lowercase.
> {code}
> > CREATE TABLE truncate_demo (x INT);
> Query: create TABLE truncate_demo (x INT)
>  > SELECT * FROM truncate_demo;
> Query: select * FROM truncate_demo
> {code}
> Notice how 'create' and 'select' were lowercased, while all other keywords were left with their original case. For me, the point of the Query: line is to have a conveniently copy-and-pasteable version of the original statement that I can put into a script or a document. If the case gets changed at all, that means some editing is required afterwards, which defeats the purpose.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)