[
https://issues.apache.org/jira/browse/IGNITE-9054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16578378#comment-16578378
]
ASF GitHub Bot commented on IGNITE-9054:
----------------------------------------
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4529
IGNITE-9054 Avoid using OptimizedMarshaller with ScanQuery initial.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9054
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4529.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4529
----
commit 2c66454e753e97db94d626d1ca1adba875cdb1f3
Author: Ilya Kasnacheev <ilya.kasnacheev@...>
Date: 2018-08-13T14:54:52Z
IGNITE-9054 Avoid using OptimizedMarshaller with ScanQuery initial.
----
> 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)
