[ https://issues.apache.org/jira/browse/IGNITE-12381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995768#comment-16995768 ]
Alexandr Shapkin commented on IGNITE-12381: ------------------------------------------- Hello [~oleg_bonar], I just realized, that there is a big incoming feature about replacing H2 with Calcite. [https://cwiki.apache.org/confluence/display/IGNITE/IEP-37%3A+New+query+execution+engine] I think it's worth to start a separate topic at dev list (d...@ignite.apache.org) and discuss the details. > QueryParser: propagate H2 ErrorCode to IgniteSQLException > --------------------------------------------------------- > > Key: IGNITE-12381 > URL: https://issues.apache.org/jira/browse/IGNITE-12381 > Project: Ignite > Issue Type: Improvement > Components: sql > Affects Versions: 2.7.6 > Reporter: Alexandr Shapkin > Priority: Major > Labels: newbie > > QueryParser#parseH2 method generalizes all h2 error codes as > IgniteQueryErrorCode.PARSING > Whereas the actual error code could be more specific, like > [TABLE_OR_VIEW_NOT_FOUND_1|https://www.h2database.com/javadoc/org/h2/api/ErrorCode.html#c42102] > = 42102 > Let's try to convert those codes into the appropriate IgniteQueryErrorCode > values as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)