ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raul Kripalani <r...@evosent.com>
Subject Re: Let's make cache name not null in ignite 2.0
Date Thu, 02 Jun 2016 17:05:22 GMT
On Thu, Jun 2, 2016 at 5:56 PM, Alexey Kuznetsov <akuznetsov@gridgain.com>
wrote:

> 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.
>

​Ok. I would +1 the change too.​ Such API changes are exactly what major
releases are for, and allowing "null" as a cache name seems more like a
leftover than an actual functionality that one would desire.

Cheers.

---
Raúl Kripalani
linkedin.com/in/raulkripalani | evosent.com
<http://evosent.com/?utm_source=email&utm_medium=email&utm_campaign=evosent_raul>
| blog: raul.io
<http://raul.io?utm_source=email&utm_medium=email&utm_campaign=evosent_raul>
|
+34 679 52 41 75 | skype: raul.fuse

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