[
https://issues.apache.org/jira/browse/IGNITE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365883#comment-16365883
]
Vyacheslav Koptilin commented on IGNITE-7649:
---------------------------------------------
Hi [~zstan]
The proposed fix assumes the transformer is transferred via network every time
when a new page requested. It seems to me, this approach is not efficient.
I think that the transformer should be cached on the remote node, for example,
within {{ScanIterator}}.
Please see details here: https://issues.apache.org/jira/browse/IGNITE-5804
So I will close this ticket as a duplicate.
> transformer instance is not properly transfers into ScanQuery request.
> ----------------------------------------------------------------------
>
> Key: IGNITE-7649
> URL: https://issues.apache.org/jira/browse/IGNITE-7649
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.3
> Reporter: Stanilovsky Evgeny
> Assignee: Stanilovsky Evgeny
> Priority: Major
> Fix For: 2.5
>
> Attachments: 222.png
>
>
> to reproduce this case we need some simple changes in existing test:
> GridCacheQueryTransformerSelfTest#testKeepBinary
> change:
> {code:java}
> List<Integer> res = binaryCache.query(new ScanQuery<Integer, BinaryObject>(),
> transformer).getAll();{code}
> into:
> {code:java}
> List<Integer> res = binaryCache.query(new ScanQuery<Integer,
> BinaryObject>().setPageSize(2), transformer).getAll();{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
