[ 
https://issues.apache.org/jira/browse/HIVE-15820?focusedWorklogId=530520&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-530520
 ]

ASF GitHub Bot logged work on HIVE-15820:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 04/Jan/21 06:11
            Start Date: 04/Jan/21 06:11
    Worklog Time Spent: 10m 
      Work Description: ujc714 commented on pull request #1814:
URL: https://github.com/apache/hive/pull/1814#issuecomment-753778414


   The function trim() is called by HiveStringUtils.removeComments(String, 
int[]). As HiveStringUtils.removeComments(String, int[]) process a multiline 
statement as a single line string, only the leading spaces in the first line 
and the trailing spaces in the last line are removed. After I replaced 
HiveStringUtils.removeComments(String, int[]) with 
HiveStringUtils.removeComments(String), the leading spaces and trailing spaces 
in each line are trimmed. It's why 6 tests failed.
   
   Rather than change HiveStringUtils.removeComments(String, int[]), I changed 
the test files as the new behaviour is expected.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 530520)
    Time Spent: 20m  (was: 10m)

> comment at the head of beeline -e
> ---------------------------------
>
>                 Key: HIVE-15820
>                 URL: https://issues.apache.org/jira/browse/HIVE-15820
>             Project: Hive
>          Issue Type: Bug
>          Components: Beeline
>    Affects Versions: 1.2.1, 2.1.1
>            Reporter: muxin
>            Assignee: muxin
>            Priority: Major
>              Labels: patch, pull-request-available
>         Attachments: HIVE-15820.patch
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> $ beeline -u jdbc:hive2://localhost:10000 -n test -e "
> > --asdfasdfasdfasdf
> > select * from test_table;
> > "
> expected result of the above command should be all rows of test_table(same as 
> run in beeline interactive mode),but it does not output anything.
> the cause is that -e option will read commands as one string, and in method 
> dispatch(String line) it calls function isComment(String line) in the first, 
> which using
>  'lineTrimmed.startsWith("#") || lineTrimmed.startsWith("--")' 
> to regard commands as a comment.
> two ways can be considered to fix this problem:
> 1. in method initArgs(String[] args), split command by '\n' into command list 
> before dispatch when cl.getOptionValues('e') != null
> 2. in method dispatch(String line), remove comments using this:
> static String removeComments(String line) {
>     if (line == null || line.isEmpty()) {
>         return line;
>     }
>     StringBuilder builder = new StringBuilder();
>     int escape = -1;
>     for (int index = 0; index < line.length(); index++) {
>         if (index < line.length() - 1 && line.charAt(index) == 
> line.charAt(index + 1)) {
>             if (escape == -1 && line.charAt(index) == '-') {
>                 //find \n as the end of comment
>                 index = line.indexOf('\n',index+1);
>                 //there is no sql after this comment,so just break out
>                 if (-1==index){
>                     break;
>                 }
>             }
>         }
>         char letter = line.charAt(index);
>         if (letter == escape) {
>             escape = -1; // Turn escape off.
>         } else if (escape == -1 && (letter == '\'' || letter == '"')) {
>             escape = letter; // Turn escape on.
>         }
>         builder.append(letter);
>     }
>     return builder.toString();
>   }
> the second way can be a general solution to remove all comments start with 
> '--'  in a sql



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to