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

Namit Jain updated HIVE-3530:
-----------------------------

    Description: 
     Building Grammar 
/Users/njain/hive/hive3/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g  ....
     ANTLR Parser Generator  Version 3.0.1 (August 13, 2007)  1989-2007
     warning(200): 
/Users/njain/hive/hive3/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g:578:5:
 Decision can match input such as "Identifier KW_RENAME KW_TO" using multiple 
alternatives: 1, 10
     As a result, alternative(s) 10 were disabled for that input
     warning(200): 
/Users/njain/hive/hive3/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g:1607:5:
 Decision can m
atch input such as "Identifier DOT Identifier" using multiple alternatives: 1, 2
     As a result, alternative(s) 2 were disabled for that input
     warning(200): 
/Users/njain/hive/hive3/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g:1823:5:
 Decision can match input such as "KW_ORDER KW_BY LPAREN" using multiple 
alternatives: 1, 2
     As a result, alternative(s) 2 were disabled for that input
     warning(200): 
/Users/njain/hive/hive3/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g:1836:5:
 Decision can match input such as "KW_CLUSTER KW_BY LPAREN" using multiple 
alternatives: 1, 2
     As a result, alternative(s) 2 were disabled for that input
     warning(200): 
/Users/njain/hive/hive3/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g:1848:5:
 Decision can match input such as "KW_DISTRIBUTE KW_BY LPAREN" using multiple 
alternatives: 1, 2
     As a result, alternative(s) 2 were disabled for that input
     warning(200): 
/Users/njain/hive/hive3/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g:1859:5:
 Decision can match input such as "KW_SORT KW_BY LPAREN" using multiple 
alternatives: 1, 2
     As a result, alternative(s) 2 were disabled for that input


Most of these seem to be due to HIVE-1367


  was:
     [echo] Building Grammar 
/Users/njain/hive/hive3/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g  ....
     [java] ANTLR Parser Generator  Version 3.0.1 (August 13, 2007)  1989-2007
     [java] warning(200): 
/Users/njain/hive/hive3/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g:578:5:
 Decision can ma\
tch input such as "Identifier KW_RENAME KW_TO" using multiple alternatives: 1, 
10
     [java] As a result, alternative(s) 10 were disabled for that input
     [java] warning(200): 
/Users/njain/hive/hive3/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g:1607:5:
 Decision can m\
atch input such as "Identifier DOT Identifier" using multiple alternatives: 1, 2
     [java] As a result, alternative(s) 2 were disabled for that input
     [java] warning(200): 
/Users/njain/hive/hive3/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g:1823:5:
 Decision can m\
atch input such as "KW_ORDER KW_BY LPAREN" using multiple alternatives: 1, 2
     [java] As a result, alternative(s) 2 were disabled for that input
     [java] warning(200): 
/Users/njain/hive/hive3/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g:1836:5:
 Decision can m\
atch input such as "KW_CLUSTER KW_BY LPAREN" using multiple alternatives: 1, 2
     [java] As a result, alternative(s) 2 were disabled for that input
     [java] warning(200): 
/Users/njain/hive/hive3/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g:1848:5:
 Decision can m\
atch input such as "KW_DISTRIBUTE KW_BY LPAREN" using multiple alternatives: 1, 
2
     [java] As a result, alternative(s) 2 were disabled for that input
     [java] warning(200): 
/Users/njain/hive/hive3/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g:1859:5:
 Decision can m\
atch input such as "KW_SORT KW_BY LPAREN" using multiple alternatives: 1, 2
     [java] As a result, alternative(s) 2 were disabled for that input


Most of these seem to be due to HIVE-1367


    
> warnings in Hive.g
> ------------------
>
>                 Key: HIVE-3530
>                 URL: https://issues.apache.org/jira/browse/HIVE-3530
>             Project: Hive
>          Issue Type: Bug
>          Components: Query Processor
>            Reporter: Namit Jain
>
>      Building Grammar 
> /Users/njain/hive/hive3/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g  
> ....
>      ANTLR Parser Generator  Version 3.0.1 (August 13, 2007)  1989-2007
>      warning(200): 
> /Users/njain/hive/hive3/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g:578:5:
>  Decision can match input such as "Identifier KW_RENAME KW_TO" using multiple 
> alternatives: 1, 10
>      As a result, alternative(s) 10 were disabled for that input
>      warning(200): 
> /Users/njain/hive/hive3/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g:1607:5:
>  Decision can m
> atch input such as "Identifier DOT Identifier" using multiple alternatives: 
> 1, 2
>      As a result, alternative(s) 2 were disabled for that input
>      warning(200): 
> /Users/njain/hive/hive3/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g:1823:5:
>  Decision can match input such as "KW_ORDER KW_BY LPAREN" using multiple 
> alternatives: 1, 2
>      As a result, alternative(s) 2 were disabled for that input
>      warning(200): 
> /Users/njain/hive/hive3/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g:1836:5:
>  Decision can match input such as "KW_CLUSTER KW_BY LPAREN" using multiple 
> alternatives: 1, 2
>      As a result, alternative(s) 2 were disabled for that input
>      warning(200): 
> /Users/njain/hive/hive3/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g:1848:5:
>  Decision can match input such as "KW_DISTRIBUTE KW_BY LPAREN" using multiple 
> alternatives: 1, 2
>      As a result, alternative(s) 2 were disabled for that input
>      warning(200): 
> /Users/njain/hive/hive3/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g:1859:5:
>  Decision can match input such as "KW_SORT KW_BY LPAREN" using multiple 
> alternatives: 1, 2
>      As a result, alternative(s) 2 were disabled for that input
> Most of these seem to be due to HIVE-1367

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to