You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Valentin Kulichenko <va...@gmail.com> on 2016/02/26 23:09:51 UTC
Creating client caches if 'schema not found' exception is thrown
Folks,
We have a pretty serious issue [1] that potentially breaks cross-cache
queries in JDBC driver and in other integrations like Zeppelin interpreter,
Spark, etc.
I made a simple fix - catch the exception and create all client caches that
are currently missing.
Can someone review my changes in branch 'ignite-2455'? I will merge them to
master after TC passes.
[1] https://issues.apache.org/jira/browse/IGNITE-2455
-Val
Re: Creating client caches if 'schema not found' exception is thrown
Posted by Valentin Kulichenko <va...@gmail.com>.
Sergi,
That's a good point, thanks. I will double-check this.
-Val
On Sat, Feb 27, 2016 at 12:04 PM, Sergi Vladykin <se...@gmail.com>
wrote:
> Val,
>
> I didn't look at the code but I hope you've covered case when schema name
> is configured to be different from the cache name?
>
> Sergi
>
> 2016-02-27 2:34 GMT+03:00 Alexey Goncharuk <al...@gmail.com>:
>
> > Looks good to me.
> >
>
Re: Creating client caches if 'schema not found' exception is thrown
Posted by Sergi Vladykin <se...@gmail.com>.
Val,
I didn't look at the code but I hope you've covered case when schema name
is configured to be different from the cache name?
Sergi
2016-02-27 2:34 GMT+03:00 Alexey Goncharuk <al...@gmail.com>:
> Looks good to me.
>
Re: Creating client caches if 'schema not found' exception is thrown
Posted by Alexey Goncharuk <al...@gmail.com>.
Looks good to me.