William Do created IGNITE-5119:
----------------------------------
Summary: Provide more descriptive errors when calling affinityRun
or affinityCall
Key: IGNITE-5119
URL: https://issues.apache.org/jira/browse/IGNITE-5119
Project: Ignite
Issue Type: Improvement
Affects Versions: 1.9
Reporter: William Do
Priority: Minor
When calling compute affinityRun or affinityCall using a cache name that
doesn't exist, an exception is thrown with the message: _Failed to get cache
affinity_.
{noformat}
Exception in thread "main" class org.apache.ignite.IgniteException: Failed to
get cache affinity.
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:946)
at
org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:201)
at
com.ultimaspin.ignite.AffinityRunExample.main(AffinityRunExample.java:28)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to get cache
affinity.
at
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition0(GridAffinityProcessor.java:192)
at
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition(GridAffinityProcessor.java:175)
at
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition(GridAffinityProcessor.java:155)
at
org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:191)
... 1 more
{noformat}
It would be nice if the message could give a more descriptive message as to why
it was unable to determine the affinity (in this case because the cache doesn't
exist).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
