You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2022/09/05 07:49:00 UTC
[jira] [Updated] (IGNITE-17090) Map sql errors to messages that user see
[ https://issues.apache.org/jira/browse/IGNITE-17090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vyacheslav Koptilin updated IGNITE-17090:
-----------------------------------------
Reviewer: Vyacheslav Koptilin
> Map sql errors to messages that user see
> ----------------------------------------
>
> Key: IGNITE-17090
> URL: https://issues.apache.org/jira/browse/IGNITE-17090
> Project: Ignite
> Issue Type: Task
> Reporter: Aleksandr
> Assignee: Aleksandr
> Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> There is a number of errors that user can get during sql command execution. Map all types of errors and map them to exit error codes and user messages. Also, a user has to understand what is wrong with the query. Now it displays jusn an abstract message.
>
> How it works now:
> {code:java}
> sql-cli> create table myta
> SQL query parsing error: Sql query execution failed.
> sql-cli> {code}
> {code:java}
> sql-cli> create table mytable(i int, j int);
> Unrecognized error while process SQL query.
> sql-cli> {code}
> "SQL query parsing error: Sql query execution failed.", "Unrecognized error while process SQL query." say nothing about {*}what exactly is wrong{*}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)