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

Attila Turoczy updated HIVE-29664:
----------------------------------
    Description: 
Beeline is the classic CLI SQL client for Hive. Currently, the query editor is 
plain text only and does not provide any syntax highlighting for Hive SQL. This 
makes it harder for users to read queries, identify keywords, and quickly 
notice mistyped SQL statements.

To improve usability, Beeline should support basic Hive SQL syntax 
highlighting. The implementation can start with a static list of commonly used 
Hive SQL keywords, such as {*}SELECT{*}, {*}INSERT{*}, {*}JOIN{*}, {*}WHERE{*}, 
*GROUP BY, ORDER BY, CREATE, DROP, ALTER,* and others.

The syntax highlighting should be enabled by default to provide a better user 
experience out of the box. However, users should also have a configuration 
option or command-line flag to disable it when needed, for example in 
environments where plain text output is preferred or required.

> Add syntax highlight support for beeline
> ----------------------------------------
>
>                 Key: HIVE-29664
>                 URL: https://issues.apache.org/jira/browse/HIVE-29664
>             Project: Hive
>          Issue Type: New Feature
>          Components: Beeline
>            Reporter: Attila Turoczy
>            Assignee: Attila Turoczy
>            Priority: Major
>
> Beeline is the classic CLI SQL client for Hive. Currently, the query editor 
> is plain text only and does not provide any syntax highlighting for Hive SQL. 
> This makes it harder for users to read queries, identify keywords, and 
> quickly notice mistyped SQL statements.
> To improve usability, Beeline should support basic Hive SQL syntax 
> highlighting. The implementation can start with a static list of commonly 
> used Hive SQL keywords, such as {*}SELECT{*}, {*}INSERT{*}, {*}JOIN{*}, 
> {*}WHERE{*}, *GROUP BY, ORDER BY, CREATE, DROP, ALTER,* and others.
> The syntax highlighting should be enabled by default to provide a better user 
> experience out of the box. However, users should also have a configuration 
> option or command-line flag to disable it when needed, for example in 
> environments where plain text output is preferred or required.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to