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 2023/07/28 07:45:00 UTC
[jira] [Commented] (IGNITE-14865) Error handling in SQL module
[ https://issues.apache.org/jira/browse/IGNITE-14865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748455#comment-17748455 ]
Pavel Pereslegin commented on IGNITE-14865:
-------------------------------------------
Task for table/view exception handling already exists: https://issues.apache.org/jira/browse/IGNITE-14500
> Error handling in SQL module
> ----------------------------
>
> Key: IGNITE-14865
> URL: https://issues.apache.org/jira/browse/IGNITE-14865
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Yury Gerzhedovich
> Assignee: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> SQL is a part of pubic API and should throw only public exceptions. Let's make sure that it will be true by adding conversation from internal exception to public one
> on a border of the transition from the internal to the public part.
> The ticket should be based on result of IGNITE-19539
> Also let's check KV view, Binary view, and fix it here or create separe tickets in case it require many changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)