[jira] [Created] (IGNITE-20943) IndexQuery requires custom key and value Java objects on classpath for thin clients but not fat clients

["Gary Henderson (Jira)" <ji...@apache.org>]

Gary Henderson created IGNITE-20943:
---------------------------------------

             Summary: IndexQuery requires custom key and value Java objects on classpath for thin clients but not fat clients
                 Key: IGNITE-20943
                 URL: https://issues.apache.org/jira/browse/IGNITE-20943
             Project: Ignite
          Issue Type: Bug
          Components: binary
    Affects Versions: 2.15
         Environment: v2.15.0

Java 1.8+

Three nodes

SSL enabled

Native persistence

Custom network timeout values

RestartProcessFailureHandler

Custom SegmentationPluginProvider

 
            Reporter: Gary Henderson


When performing index queries from thin clients, the Ignite node always attempts to deserialise the key and value pairs internally before returning data to the thin client and thus requires the key and value Java objects to be available on the node's classpath but this is not the case for fat clients - only the client itself needs to have access to the Java objects.

The fat client behaviour is the expected behaviour because this matches the normal ScanQuery behaviour for both fat and thin clients.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)