[
https://issues.apache.org/jira/browse/IGNITE-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026082#comment-16026082
]
ASF GitHub Bot commented on IGNITE-4667:
----------------------------------------
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/2012
IGNITE-4667 - Throw exception on starting client cache when indexed t…
…ypes cannot be loaded
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4667-master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2012.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 #2012
----
commit 22a64e30a3e1e7cac322a520d12cfd7cb179c524
Author: dkarachentsev <[email protected]>
Date: 2017-05-26T09:55:55Z
IGNITE-4667 - Throw exception on starting client cache when indexed types
cannot be loaded
----
> Throw exception on starting client cache when indexed types cannot be loaded
> ----------------------------------------------------------------------------
>
> Key: IGNITE-4667
> URL: https://issues.apache.org/jira/browse/IGNITE-4667
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.8
> Reporter: Dmitry Karachentsev
> Assignee: Dmitry Karachentsev
> Fix For: 2.1
>
>
> Assume following situation:
> 1. Server node configured cache indexed types with classes that client node
> doesn't have.
> 2. Start server.
> 3. Start client. Client successfully connected.
> 4. Try to get cache on client node.
> 5. Was thrown exception in GridQueryProcessor and request for cache on client
> node hangs forever.
> If on some reason cache couldn't be initialized, exception must be thrown on
> Ignite.cache() operation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
