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

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

                Author: ASF GitHub Bot
            Created on: 19/Mar/21 09:50
            Start Date: 19/Mar/21 09:50
    Worklog Time Spent: 10m 
      Work Description: zeroflag commented on a change in pull request #2059:
URL: https://github.com/apache/hive/pull/2059#discussion_r597539014



##########
File path: hplsql/src/test/results/local/func_no_return.out.txt
##########
@@ -0,0 +1 @@
+Ln:1 identifier 'CREATE' must be declared.

Review comment:
       Yes, generated parsers rarely give very good error messages unlike 
handwritten parsers. I think it is still an improvement over what we used to 
have (silently ignored incorrect syntax). If you have an idea how to make antlr 
emit  better error messages please let me know.




-- 
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: 568860)
    Time Spent: 0.5h  (was: 20m)

> Improve validation and error handling in HPL/SQL 
> -------------------------------------------------
>
>                 Key: HIVE-24315
>                 URL: https://issues.apache.org/jira/browse/HIVE-24315
>             Project: Hive
>          Issue Type: Sub-task
>          Components: hpl/sql
>            Reporter: Attila Magyar
>            Assignee: Attila Magyar
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> There are some known issues that need to be fixed. For example it seems that 
> arity of a function is not checked when calling it, and same is true for 
> parameter types. Calling an undefined function is evaluated to null and 
> sometimes it seems that incorrect syntax is silently ignored. 
> In cases like this a helpful error message would be expected, thought we 
> should also consider how PL/SQL works and maintain compatibility.



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

Reply via email to