ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Kuznetsov <akuznet...@gridgain.com>
Subject Re: Let's make cache name not null in ignite 2.0
Date Thu, 02 Jun 2016 16:56:34 GMT
Dmitriy,

I'm talking about possible *** IGNITE 2.0 *** that may be not released
several years :)
I think it will contain a LOT of API changes anyway.
Adding one more change should not be a show stopper?
Or I'm missing something?

Raul,

User can create cache via Spring XML and simply not specify property "name".
And Yes, Ignite will take null without any warning.

I think we at least should start to print warning in current Ignite 1.x.


On Thu, Jun 2, 2016 at 11:46 PM, Raul Kripalani <raulk@apache.org> wrote:

> ​Hey,​
>
> On Thu, Jun 2, 2016 at 5:21 PM, Dmitriy Setrakyan <dsetrakyan@apache.org>
> wrote:
>
> > Anyone here is even considering the compatibility impact it will have on
> > our users? I am still struggling to find a single reason for how it would
> > benefit our user base.
> >
>
> ​I've been away for some time. Under what circumstances can you create a
> cache with null name?
>
>
> https://ignite.apache.org/releases/mobile/org/apache/ignite/Ignite.html#cache(java.lang.String)
>
> https://ignite.apache.org/releases/mobile/org/apache/ignite/cache/CacheManager.html#getCache(java.lang.String)
>
> They both require a cache name as an argument.
>
> Do you mean that the user could explicitly pass null as an argument, and
> that was something that Ignite swallowed without complaining?
>
> Cheers.
>
> ---
> Raúl Kripalani
> linkedin.com/in/raulkripalani | evosent.com
> <http://evosent.com/?utm_source=email&utm_medium=email&utm_campaign=apache>
> |
> blog: raul.io | skype: raul.fuse
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message