[
https://issues.apache.org/jira/browse/IGNITE-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083706#comment-16083706
]
ASF GitHub Bot commented on IGNITE-5123:
----------------------------------------
GitHub user YevIgn opened a pull request:
https://github.com/apache/ignite/pull/2285
IGNITE-5123
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/YevIgn/ignite ignite-5123
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2285.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2285
----
commit b329b100549d6608f126bc35c9cc62c2e6e693e7
Author: Evgeniy Ignatiev <[email protected]>
Date: 2017-07-12T09:33:06Z
IGNITE-5123 Reorder ignite plugin provider on Ignite start callback call
So that PluginProvider#onIgniteStart will be called after internal
components start callbacks have been executed to comply with itself
javadoc.
----
> 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
> 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)
