[
https://issues.apache.org/jira/browse/HIVE-26900?focusedWorklogId=853741&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-853741
]
ASF GitHub Bot logged work on HIVE-26900:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 29/Mar/23 16:58
Start Date: 29/Mar/23 16:58
Worklog Time Spent: 10m
Work Description: shreeyasand closed pull request #4168: HIVE-26900:
Error message not representing the correct line number wi…
URL: https://github.com/apache/hive/pull/4168
Issue Time Tracking
-------------------
Worklog Id: (was: 853741)
Time Spent: 1h 20m (was: 1h 10m)
> Error message not representing the correct line number with a syntax error in
> a HQL File
> ----------------------------------------------------------------------------------------
>
> Key: HIVE-26900
> URL: https://issues.apache.org/jira/browse/HIVE-26900
> Project: Hive
> Issue Type: Bug
> Affects Versions: 3.1.2, 4.0.0-alpha-1, 4.0.0-alpha-2
> Reporter: Vikram Ahuja
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> When a wrong syntax is added in a HQL file, the error thrown by beeline while
> running the HQL file is having the wrong line number. The line number and
> even the position is incorrect. Seems like parser is not considering spaces
> and new lines and always throwing the error on line number 1 irrespective of
> what line the error is on in the HQL file
>
> For instance, consider the following test.hql file:
> # --comment
> # --comment
> # SET hive.server2.logging.operation.enabled=true;
> # SET hive.server2.logging.operation.level=VERBOSE;
> # show tables;
> #
> #
> # CREATE TABLEE DUMMY;
>
> when we call !run test.hql in beeline or trigger ./beeline -u
> jdbc:hive2://localhost:10000 -f test.hql, The issue thrown by beeline is
> >>> CREATE TABLEE DUMMY;
> Error: Error while compiling statement: FAILED: ParseException line 1:7
> cannot recongize input near 'CREATE' 'TABLEE' 'DUMMY' in ddl statement
> (state=42000,code=40000)
> The parser seems to be taking all the lines from 1 and is ignoring spaces in
> the line.
> The error line in the parse exception is shown as 1:7 but it should have been
> 8:13.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)