ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: Let's make cache name not null in ignite 2.0
Date Wed, 01 Jun 2016 22:49:48 GMT
-1

I don’t think this will give us any advantage other than many frustrated
users who will need to change their code. We should definitely discourage
using nulls though.

D.

On Wed, Jun 1, 2016 at 12:37 AM, Vladimir Ozerov <vozerov@gridgain.com>
wrote:

> +1
>
> I would also restrict nulls for node names, for IGFS names, etc..
>
> On Wed, Jun 1, 2016 at 10:29 AM, Alexey Kuznetsov <akuznetsov@gridgain.com
> >
> wrote:
>
> > Hi, All!
> >
> > In ignite-1.x cache.name could be null.
> >
> > And we have to write a lot of code to handle such name, especially in
> tools
> > like web console and Visor.
> >
> > In ignite 2.0 we could change API and make cache.name not null.
> >
> > What do you think about such change?
> >
> > It is worth to create such issue in JIRA?
> >
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>

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