ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IGNITE-7045) Client queries should throw a correct exception
Date Wed, 06 Dec 2017 10:39:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vladimir Ozerov resolved IGNITE-7045.
-------------------------------------
    Resolution: Duplicate

> Client queries should throw a correct exception
> -----------------------------------------------
>
>                 Key: IGNITE-7045
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7045
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>    Affects Versions: 2.3
>            Reporter: Kirill Shirokov
>
> The following test being added to org.apache.ignite.internal.processors.cache.distributed.replicated.IgniteCacheReplicatedQuerySelfTest:
>     /**
>      * Method verifies that in the case of client query index is not used and a correct
exception is thrown.
>      *
>      * @throws Exception If failed.
>      */
>     public void testClientOnlyNodeIndexException() throws Exception {
>         try {
>             Ignite g = startGrid("client");
>             IgniteCache<Integer, Integer> c = jcache(g, Integer.class, Integer.class);
>             try {
>                 List<List<?>> cres = c.query(new SqlFieldsQuery("select count(*)
from Integer")
>                     .setLocal(true)).getAll();
>             } 
>             catch (IgniteException e) {
>                 throw e; // FIXME: put an exception-checking code here instead of throw
>             }
>         }
>         finally {
>             stopGrid("client");
>         }
>     }
> ...will result in NPE instead of an Ignite exception explaining the appropriate cause.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message