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 certainly makes
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 years ago. C
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,
>
> It's about lo
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 will be hel
Hello!
I don't think there's a direct link between an exception thrown in depths
of Ignite code, and specific error which may be reported to user.
A notorious example is CorruptedTreeException which is known to be thrown
due to incorrect field type in binary object or bad SQL cast. So we could
do
