Alexey Scherbakov created IGNITE-14611:
--
Summary: Implement error handling for public API based on error
codes
Key: IGNITE-14611
URL: https://issues.apache.org/jira/browse/IGNITE-14611
Project
Val, excellent, thanks.
Here is the ticket: https://issues.apache.org/jira/browse/IGNITE-3690
Mike, feel free to put useful pointers there.
-
Denis
On Tue, Jan 5, 2021 at 2:31 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Mike, Denis,
>
> Having error codes
Mike, Denis,
Having error codes certainly makes sense. Please send the ticket link, and
we'll go from there.
-Val
On Mon, Jan 4, 2021 at 7:50 PM Denis Magda wrote:
> Do back this idea up of having a glossary of common errors. There is even
> a ticket for that I created a couple of yea
Do back this idea up of having a glossary of common errors. There is even a
ticket for that I created a couple of years ago. Can search for it later.
Val, how about the 3.0 suggestion? Let’s introduce error codes.
On Monday, January 4, 2021, Michael Cherkasov
wrote:
> Hi Ilya,
>
> I
Hi Ilya,
It's about logs only, I don't think we need this at the API level. Error
codes will make the solutions more searchable.
Plus we can build troubleshooting guides based on it, it will help us
gather information from user list and StackOverflow.
Even a solution for trivial cases
u google exceptions or error messages and the results can be
> ambiguous and not certain because different errors can have similar
> exceptions and you need to analyze stack trace to distinguish them. So
> googling isn't a straight and easy process in this case.
> Almost all major DBs have er
to distinguish them. So
googling isn't a straight and easy process in this case.
Almost all major DBs have error codes[1][2][3]
Let's do the same for Ignite, error codes easy to google, so user/dev list
will be significantly more useful. We can have documentation with an error
code registry and solutions
are Ignite specific codes, they are returned when queries are run via
> Ignite API. There are no codes explicitly shared by JDBC and ODBC, although
> some of them happen to be the same.
>
> Thanks, Alex. Now it sounds that we propagate these codes to JDBC and ODBC
> drivers right? In that case, we should have Generic Error Codes pages in
> documentation which lists all the common error codes, right?
>
Denis Magda created IGNITE-6687:
---
Summary: SQL Error Codes Documentation
Key: IGNITE-6687
URL: https://issues.apache.org/jira/browse/IGNITE-6687
Project: Ignite
Issue Type: Task
Security
happen to be the same.
>
Thanks, Alex. Now it sounds that we propagate these codes to JDBC and ODBC
drivers right? In that case, we should have Generic Error Codes pages in
documentation which lists all the common error codes, right?
On Thu, Oct 19, 2017 at 9:48 AM, Vladimir Ozerov <voze...@gridgain.com>
wrote:
> No, they are not re-used. SQLSTATE is JDBC/ODBC-specific thing (and both
> driver types have different codes).
>
Vladimir, are there any error codes that come from the Ignite engine that
are shar
> Vladimir, Alex P.,
>
> Do we reuse the error codes developed for JDBC on the native APIs side
> (Java, .NET, C++)? On the JDBC page we say that the codes are ANSI SQL
> compliant and my guess that they have to be the same across all SQL APIs.
>
> —
> Denis
>
> > On Oct 19
Igor,
Do you have them documented somewhere? Couldn’t find in the existing docs.
Vladimir, Alex P.,
Do we reuse the error codes developed for JDBC on the native APIs side (Java,
.NET, C++)? On the JDBC page we say that the codes are ANSI SQL compliant and
my guess that they have
Error codes are different for ODBC and JDBC.
Best Regards,
Igor
On Thu, Oct 19, 2017 at 3:23 AM, Denis Magda <dma...@apache.org> wrote:
> Alex P, Vladimir,
>
> Please confirm that the error codes documented for JDBC [1] driver are
> shared by all SQL APIs we have. If it’s
Alex P, Vladimir,
Please confirm that the error codes documented for JDBC [1] driver are shared
by all SQL APIs we have. If it’s so I would create Error Codes page under SQL
Reference section and will provide error handling code snippets for JDBC, ODBC
and the native APIs.
[1] https
Vladimir Ozerov created IGNITE-6414:
---
Summary: Document SQLSTATE error codes
Key: IGNITE-6414
URL: https://issues.apache.org/jira/browse/IGNITE-6414
Project: Ignite
Issue Type: Task
Vladimir Ozerov created IGNITE-6317:
---
Summary: JDBC thick driver: SQLSTATE error codes
Key: IGNITE-6317
URL: https://issues.apache.org/jira/browse/IGNITE-6317
Project: Ignite
Issue Type
Vladimir Ozerov created IGNITE-6294:
---
Summary: ODBC: Propagate SQLSTATE error codes
Key: IGNITE-6294
URL: https://issues.apache.org/jira/browse/IGNITE-6294
Project: Ignite
Issue Type: Task
Denis Magda created IGNITE-5620:
---
Summary: Meaningful error codes and types of exceptions for SQL
operations
Key: IGNITE-5620
URL: https://issues.apache.org/jira/browse/IGNITE-5620
Project: Ignite
19 matches
Mail list logo
