You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Pereslegin (Jira)" <ji...@apache.org> on 2024/09/25 10:26:00 UTC
[jira] [Updated] (IGNITE-23269) Sql. Reduce try/catch block used to wrap Exception into RUNTIME_ERR SqlException in ScanNode#push
[ https://issues.apache.org/jira/browse/IGNITE-23269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Pereslegin updated IGNITE-23269:
--------------------------------------
Component/s: sql
> Sql. Reduce try/catch block used to wrap Exception into RUNTIME_ERR SqlException in ScanNode#push
> -------------------------------------------------------------------------------------------------
>
> Key: IGNITE-23269
> URL: https://issues.apache.org/jira/browse/IGNITE-23269
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Pavel Pereslegin
> Priority: Major
>
> Currently in ScanNode#push we handling Exception and wrapping it into SqlException with RUNTIME_ERR code.
> Looks like it's done only to handle possible errors from user-side in statement
> {code:java}
> inst = func.createInstance(context());
> {code}
> But this try/catch block is wider then required.
> For example we can catch QueryCancelledException and wrap it into RUNTIME_ERR-exception, or other internal errors wrap into RUNTIME_ERR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)