[jira] [Updated] (IGNITE-15247) JDBC driver for 3.0: Error handling.
[ https://issues.apache.org/jira/browse/IGNITE-15247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-15247: --- 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 was: *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 > JDBC driver for 3.0: Error handling. > > > Key: IGNITE-15247 > URL: https://issues.apache.org/jira/browse/IGNITE-15247 > Project: Ignite > Issue Type: New Feature > Components: jdbc >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > *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 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15247) JDBC driver for 3.0: Error handling.
[ https://issues.apache.org/jira/browse/IGNITE-15247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-15247: --- Epic Link: IGNITE-14858 > JDBC driver for 3.0: Error handling. > > > Key: IGNITE-15247 > URL: https://issues.apache.org/jira/browse/IGNITE-15247 > Project: Ignite > Issue Type: New Feature > Components: jdbc >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > *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 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15247) JDBC driver for 3.0: Error handling.
[ https://issues.apache.org/jira/browse/IGNITE-15247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15247: -- 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 was: *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. Vendor codes must be well-documented. Let's map Ignite exceptions/error codes to proper SQLException with SQLState. > JDBC driver for 3.0: Error handling. > > > Key: IGNITE-15247 > URL: https://issues.apache.org/jira/browse/IGNITE-15247 > Project: Ignite > Issue Type: New Feature > Components: jdbc >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > *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 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15247) JDBC driver for 3.0: Error handling.
[ https://issues.apache.org/jira/browse/IGNITE-15247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15247: -- 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. Vendor codes must be well-documented. Let's map Ignite exceptions/error codes to proper SQLException with SQLState. was: *Motivation:* JDBC driver must throws exceptions of type java.sql.SQLException with mandatory SQLState codes (vendor code and standard, if exists). These codes must be documented. Let's * Create list of supported SQLState codes. * Map existed Ignite exceptions/error codes to proper SQLState > JDBC driver for 3.0: Error handling. > > > Key: IGNITE-15247 > URL: https://issues.apache.org/jira/browse/IGNITE-15247 > Project: Ignite > Issue Type: New Feature > Components: jdbc >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > *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. > Vendor codes must be well-documented. > Let's map Ignite exceptions/error codes to proper SQLException with SQLState. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15247) JDBC driver for 3.0: Error handling.
[ https://issues.apache.org/jira/browse/IGNITE-15247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15247: -- Description: *Motivation:* JDBC driver must throws exceptions of type java.sql.SQLException with mandatory SQLState codes (vendor code and standard, if exists). These codes must be documented. Let's * Create list of supported SQLState codes. * Map existed Ignite exceptions/error codes to proper SQLState was: *Motivation:* JDBC driver must throws exceptions of type java.sql.SQLException with mandatory SQLState codes (vendor code and standard, if exists). These codes must be documented. Let's use proper error codes in exceptions for failure cases and add tests. > JDBC driver for 3.0: Error handling. > > > Key: IGNITE-15247 > URL: https://issues.apache.org/jira/browse/IGNITE-15247 > Project: Ignite > Issue Type: New Feature > Components: jdbc >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > *Motivation:* > JDBC driver must throws exceptions of type java.sql.SQLException with > mandatory SQLState codes (vendor code and standard, if exists). > These codes must be documented. > Let's > * Create list of supported SQLState codes. > * Map existed Ignite exceptions/error codes to proper SQLState > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15247) JDBC driver for 3.0: Error handling.
[ https://issues.apache.org/jira/browse/IGNITE-15247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15247: -- Description: *Motivation:* JDBC driver must throws exceptions of type java.sql.SQLException with mandatory SQLState codes (vendor code and standard, if exists). These codes must be documented. Let's use proper error codes in exceptions for failure cases and add tests. was:Let's use proper error codes in exception for failure cases and add tests. > JDBC driver for 3.0: Error handling. > > > Key: IGNITE-15247 > URL: https://issues.apache.org/jira/browse/IGNITE-15247 > Project: Ignite > Issue Type: New Feature > Components: jdbc >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > *Motivation:* > JDBC driver must throws exceptions of type java.sql.SQLException with > mandatory SQLState codes (vendor code and standard, if exists). > These codes must be documented. > Let's use proper error codes in exceptions for failure cases and add tests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15247) JDBC driver for 3.0: Error handling.
[ https://issues.apache.org/jira/browse/IGNITE-15247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15247: -- Description: Let's use proper error codes in exception for failure cases and add tests. (was: h3 Motivation. JDBC API is widely used in various projects/systems. It is worth having a JDBC driver for better UX, easier integration with other systems, easier migration from the other DBs. ) > JDBC driver for 3.0: Error handling. > > > Key: IGNITE-15247 > URL: https://issues.apache.org/jira/browse/IGNITE-15247 > Project: Ignite > Issue Type: New Feature > Components: jdbc >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > Let's use proper error codes in exception for failure cases and add tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15247) JDBC driver for 3.0: Error handling.
[ https://issues.apache.org/jira/browse/IGNITE-15247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15247: -- Summary: JDBC driver for 3.0: Error handling. (was: JDBC driver for 3.0: Transactions support.) > JDBC driver for 3.0: Error handling. > > > Key: IGNITE-15247 > URL: https://issues.apache.org/jira/browse/IGNITE-15247 > Project: Ignite > Issue Type: New Feature > Components: jdbc >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > h3 Motivation. > JDBC API is widely used in various projects/systems. > It is worth having a JDBC driver for better UX, easier integration with other > systems, easier migration from the other DBs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
