[
https://issues.apache.org/jira/browse/IGNITE-9054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16603099#comment-16603099
]
ASF GitHub Bot commented on IGNITE-9054:
----------------------------------------
GitHub user alamar reopened a pull request:
https://github.com/apache/ignite/pull/4592
IGNITE-9054 Avoid using OptimizedMarshaller with initial ScanQuery.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-14092
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4592.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 #4592
----
commit d5ae876319086dacb1f7ff7fde8aed113892f744
Author: Ilya Kasnacheev <ilya.kasnacheev@...>
Date: 2018-08-22T15:17:51Z
IGNITE-9054 Avoid using OptimizedMarshaller with initial ScanQuery.
----
> 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
> Assignee: 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)
