[jira] [Comment Edited] (IGNITE-9054) ScanQuery responses are serialized with Optimized Marshaller

["Stanislav Lukyanov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-9054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16552854#comment-16552854 ] 

Stanislav Lukyanov edited comment on IGNITE-9054 at 7/23/18 1:24 PM:
---------------------------------------------------------------------

Test idea: create a custom POJO like 

{code}
    class Foo implements Serializable, Binarylizable {
        writeObject() { throw new Exception(); }
        readObject() { throw new Exception(); }
        writeBinary() { /* actual marshalling */ }
        readBinary() { /* actual marshalling */ }
    }
{code}

and use it in the queries. Ignite should never use writeObject()/readObject() if a class is Binarylizable, so if something is wrong we'll see the exceptions.


was (Author: slukyanov):
Test idea: create a custom POJO like 

    class Foo implements Serializable, Binarylizable {
        writeObject() { throw new Exception(); }
        readObject() { throw new Exception(); }
        writeBinary() { /* actual marshalling */ }
        readBinary() { /* actual marshalling */ }
    }

and use it in the queries. Ignite should never use writeObject()/readObject() if a class is Binarylizable, so if something is wrong we'll see the exceptions.

> ScanQuery responses are serialized with Optimized Marshaller
> ------------------------------------------------------------
>
>                 Key: IGNITE-9054
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9054
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 2.5
>            Reporter: Ilya Kasnacheev
>            Priority: Major
>              Labels: easyfix
>         Attachments: 22530.diff
>
>
> When you do ContinuousQuery on a cache, its initial query sends results via OptimizedMarshaller (which has binary compatibility implications) but its continuous part uses BinaryMarshaller. They should both be using BinaryMarshaller. Fix seems to be one-liner, see patch and userlist thread.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)