[ https://issues.apache.org/jira/browse/IGNITE-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095287#comment-16095287 ]
Konstantin Boudnik edited comment on IGNITE-5123 at 7/20/17 8:09 PM: --------------------------------------------------------------------- I am _not_ saying one is better than another (and the example you've provided doesn't look that much ticket specific for me, really). I am saying that splitting the discussion through the multiple sources makes it harder for people to use later. was (Author: cos): I am saying one is better than another (and the example you've provided doesn't look that much ticket specific for me, really). I am saying that splitting the discussion through the multiple sources makes it harder for people to use later. > Ignite.cache(String) returns null in PluginProvider.onIgniteStart() > ------------------------------------------------------------------- > > Key: IGNITE-5123 > URL: https://issues.apache.org/jira/browse/IGNITE-5123 > Project: Ignite > Issue Type: Bug > Affects Versions: 2.0 > Reporter: Nick Pordash > Assignee: Yevgeniy Ignatyev > Fix For: 2.2 > > Attachments: ignite-plugin-failure.zip > > > Given an Ignite node that has pre-configured caches (via > IgniteConfiguration.setCacheConfiguration) if you try to obtain a reference > to the cache instance in PluginProvider.onIgniteStart() you'll get a null > reference. > @Override > public void onIgniteStart() throws IgniteCheckedException { > ignite.cacheNames().forEach(name -> { > assert ignite.cache(name) != null : "Cache is null: " + name; > }); > } -- This message was sent by Atlassian JIRA (v6.4.14#64029)