[
https://issues.apache.org/jira/browse/CALCITE-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443193#comment-17443193
]
Julian Hyde commented on CALCITE-4877:
--------------------------------------
I have marked as fixed in Avatica 1.20. (The way I see it, the issue is fixed,
but we are still working through some CI brittleness.)
Regarding that CI brittleness. I have a PR for Calcite that makes the
{{schema.iq}} test robust enough to work against both Avatica 1.19 and Avatica
1.20-SNAPSHOT. Please review [PR
2608|https://github.com/apache/calcite/pull/2608].
> 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
> Labels: pull-request-available
> Fix For: avatica-1.20.0
>
> Attachments: image-2021-11-06-07-03-57-742.png
>
> Time Spent: 10h 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:java}
> 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}
> And would be great if we have a little bit improvement as follows:
> {code:java}
> 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.20.1#820001)
