[IGNITE-15247] JDBC driver for 3.0: Error handling.

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: jdbc
• Labels: ignite-3
• Epic Link: JDBC 3.0
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: Andrey Mashenkov
• Created: 04/Aug/21 13:18
• Updated: 13/Mar/23 14:42

Description

Motivation:
JDBC driver must throws exceptions of java.sql.SQLException kind with a SQLState code (XOPEN type or the SQL:2003 type).
Standard says SQLState is implementation-defined thing and define the SQLState format, some predefined categories and ability to specify vendor-code of 'int' type.
Vendor codes must be well-documented.

Let's map Ignite exceptions/error codes to proper SQLException with SQLState.
1. As we always know at what phase the query execution (in JDBC driver or in SQL engine) was failed, we can use proper standard SQLState category.
2. We use IGN-XXX-nnn format (where XXX is a group name and nnn is an unique error code within a group) [1], we can't map Ignite error code to SQL vendor code directly.
So, we should convert non-SQL origins to IGN-SQL-nnn somehow and use 'nnn' as vendor code..

https://issues.apache.org/jira/browse/IGNITE-14931

Issue Links

• Blocked: IGNITE-17090 Map sql errors to messages that user see
• is blocked by: IGNITE-14865 Error handling in SQL module