[ 
https://issues.apache.org/jira/browse/CALCITE-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17439571#comment-17439571
 ] 

sunjincheng edited comment on CALCITE-4877 at 11/6/21, 2:27 AM:
----------------------------------------------------------------

Hi, [~nobigo] I have open the PR here: 
https://github.com/apache/calcite-avatica/pull/161 , and would be great if you 
can do me a favor to review. :)


was (Author: sunjincheng121):
Hi, [~nobigo] I have open the PR here: 
https://github.com/apache/calcite-avatica/pull/161 , and would be great if you 
can help to review. :)

> Make the exception information of class not found more explicit
> ---------------------------------------------------------------
>
>                 Key: CALCITE-4877
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4877
>             Project: Calcite
>          Issue Type: Improvement
>          Components: avatica
>            Reporter: sunjincheng
>            Assignee: sunjincheng
>            Priority: Major
>             Fix For: 1.29.0
>
>         Attachments: image-2021-11-06-07-03-57-742.png
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Make the exception information of class not found more explicit when we want 
> REATE SCHEMA or CREATE TABLE supported.
>  when we not add the class to the class path we got the exception as follows:
> {code}
> Error: Error while executing SQL "CREATE TABLE t (i INTEGER, j VARCHAR(10))": 
> Property 'org.apache.calcite.sql.parser.ddl.SqlDdlParserImpl#FACTORY' not 
> valid for plugin type org.apache.calcite.sql.parser.SqlParserImplFactory 
> (state=,code=0)
> {code}
>  !image-2021-11-06-07-03-57-742.png! 
> {code}
>  would be great if we can make the error message more explicit , such as: 
> "Property 'org.apache.calcite.sql.parser.ddl.SqlDdlParserImpl#FACTORY' not 
> valid as 'org.apache.calcite.sql.parser.ddl.SqlDdlParserImpl' not found in 
> the classpath."  
> {code}
> What do you think?



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

Reply via email to