You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2019/02/12 09:45:00 UTC
[jira] [Closed] (IGNITE-8016) Make sure checks in
QueryUtils.typeForQueryEntity are sane
[ https://issues.apache.org/jira/browse/IGNITE-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov closed IGNITE-8016.
-----------------------------------
> Make sure checks in QueryUtils.typeForQueryEntity are sane
> ----------------------------------------------------------
>
> Key: IGNITE-8016
> URL: https://issues.apache.org/jira/browse/IGNITE-8016
> Project: Ignite
> Issue Type: Task
> Components: cache, sql
> Reporter: Alexander Paschenko
> Priority: Major
>
> If one uses {{AffinityUuid}} (and thus, most likely, any {{AffinityKey}} at all) as cache key in {{QueryEntity}} while not having an actual class for value type, cache fails to start with error
>
> {{Failed to find value class in the node classpath (use default marshaller to enable binary objects)}}
>
> Not only error message is misleading (as {{BinaryMarshaller}} is always on now), the checks themselves must be verified for sanity as ruling them out allowed to start cache, put data into it via cache API and perform SQL query that worked.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)