All we can do here is to propagate error message from H2. Probably it will give more details.
Sergi 2016-11-18 13:31 GMT+03:00 Alexey Kuznetsov <akuznet...@apache.org>: > Vasiliy, Pavel. > > I think it is a usability issue. > Not always user has a full stack trace. > For example, if I execute this query via some UI tool - in most cases I > will see only top level message. > > I have no idea how hard to implement such functionality. > > Sergi (as a most expert in SQL engine) could you estimate how hard to fix > this? > > > On Fri, Nov 18, 2016 at 5:00 PM, Pavel Tupitsyn <ptupit...@apache.org> > wrote: > >> Vasiliy, did you examine the full stack trace? >> >> I've tried an invalid query and got the following in one of the inner >> exceptions: >> Caused by: org.h2.jdbc.JdbcSQLException: Table "ORGANIZATION2" not found >> >> However, I agree that this should be present in the top level exception >> message. >> >> On Fri, Nov 18, 2016 at 10:51 AM, Vasiliy Sisko <vsi...@gridgain.com> >> wrote: >> >>> Hello Igniters. >>> >>> When I execute query: SELECT * FROM “PersonCache”.Person2 an exception >>> with the next text is thrown: “Error: Failed to parse query: ...”. >>> That message does not give information about cause of exception. >>> Possible message of exception should be like: “Table Person2 does not >>> exists” >>> >>> Is it possible to support such functionality in query engine? >>> >>> -- >>> Vasiliy Sisko >>> GridGain Systems >>> www.gridgain.com >>> >> >> > > > -- > Alexey Kuznetsov >
