Andrey, You are right. Somehow, I have not noticed that. Thanks for your help.
Best Regards, Igor On Thu, Jun 22, 2017 at 8:27 PM, Andrey Gura <ag...@apache.org> wrote: > I've commented first reply to the question. But actualy I didn't test it. > > On Thu, Jun 22, 2017 at 8:24 PM, Andrey Gura <ag...@apache.org> wrote: > > org.*h2*.jdbc.JdbcSQLException > > > > It isn't realted with JDBC. He uses schema name instead of table name > > for insert. > > > > On Thu, Jun 22, 2017 at 2:41 PM, Igor Sapego <isap...@apache.org> wrote: > >> There is still no reply for this ticket. Who can take a look? > >> Val? Andrey? > >> > >> Best Regards, > >> Igor > >> > >> On Tue, Jun 20, 2017 at 2:37 AM, Igor Rudyak <irud...@gmail.com> wrote: > >> > >>> Hi guys, > >>> > >>> According to the exception it looks like a JDBC problem, rather than > >>> Cassandra related staff. As I remember Ignite JDBC (1.8 version for > sure) > >>> uses some weird names for the tables like *<cache-name>.<java_class_ > >>> name>*. > >>> > >>> Because of this you just can't simple do "*select * from my_cache*", > but > >>> should do something like "*select * from > my_cache.my_java_class_name*". I > >>> assume that in insert statement you should also use > >>> *cache1.my_java_class_name* instead of just *cache1*. > >>> > >>> > >>> > >>> Igor > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> On Mon, Jun 19, 2017 at 4:03 PM, Dmitriy Setrakyan < > dsetrak...@apache.org> > >>> wrote: > >>> > >>> > Igor, which Igor are you asking? (no pun intended) Perhaps it makes > sense > >>> > to explicitly add him to CC. > >>> > > >>> > D. > >>> > > >>> > On Mon, Jun 19, 2017 at 4:17 PM, Igor Sapego <isap...@apache.org> > wrote: > >>> > > >>> > > Igor, > >>> > > > >>> > > Can you please take a look at this question at SO? > >>> > > > >>> > > https://stackoverflow.com/questions/44589774/configure- > >>> > > apache-ignite-cache-with-cassandra-and-odbc/44630522 > >>> > > > >>> > > Best Regards, > >>> > > Igor > >>> > > > >>> > > >>> >
