Thanks Alexey. Now it fixed and I found more issues for the release candidate:
[1] IGNITE-5122 REST example is broken <https://issues.apache.org/jira/browse/IGNITE-5122> [2] IGNITE-5121 REST API call with empty cache name causes NPE <https://issues.apache.org/jira/browse/IGNITE-5121> On Sat, Apr 29, 2017 at 5:09 PM, Alexey Kuznetsov <akuznet...@apache.org> wrote: > Sergey, > > Good cacth. I think this issue is a blocker to release. > -1 from me (binding). > > However I'v already pushed the fix, please check it. > > > On Sat, Apr 29, 2017 at 8:48 PM, Alexey Kuznetsov <akuznet...@apache.org> > wrote: > > > Nik, > > > > Thanks, that you spotted this issue. > > > > Could you provide a simple reproducer & create issue in JIRA? > > > > > > On Sat, Apr 29, 2017 at 6:03 AM, npordash <nickpord...@gmail.com> wrote: > > > >> Hi Guys, > >> > >> Sorry to post this in a voting thread, but I tried to update a project > to > >> 2.0 (using the git tag Denis referred to) and I'm seeing what I assume > is > >> a > >> regression. In short, attempts to access a pre-configured cache within > the > >> onIgniteStart() method of a PluginProvider now returns null instead of > >> returning the cache. In 1.9 this was not returning null. > >> > >> Is this an intended behavioral change? According to the javadoc it still > >> states that Ignite has fully started by the time onIgniteStart() is > >> invoked. > >> > >> Thanks! > >> -Nick > >> > >> > >> > >> -- > >> View this message in context: http://apache-ignite-developer > >> s.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-0-0-RC1-tp17335p17338.html > >> Sent from the Apache Ignite Developers mailing list archive at > Nabble.com. > >> > > > > > > > > -- > > Alexey Kuznetsov > > > > > > -- > Alexey Kuznetsov > -- Sergey Kozlov GridGain Systems www.gridgain.com
