[
https://issues.apache.org/jira/browse/IGNITE-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15760782#comment-15760782
]
Nikolay Tikhonov commented on IGNITE-3867:
------------------------------------------
[~amashenkov]
If we can't test feature how can we sure that issue gone? Any developer can
break down and do not notice it. ;) You can override {{Tcp CommunicationSpi}}
and check that page size sent to remote node and check that we received several
messages instead of one. Look at IgniteCacheAbstractStopBusySelfTest test as
example.
> ScanQuery ignores pageSize propertry
> ------------------------------------
>
> Key: IGNITE-3867
> URL: https://issues.apache.org/jira/browse/IGNITE-3867
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.7
> Reporter: Nikolay Tikhonov
> Assignee: Andrew Mashenkov
>
> See
> {{org.apache.ignite.internal.processors.cache.IgniteCacheProxy#query(ScanQuery,
> IgniteClosure<T,R>, ClusterGroup)}} method.
> In this place we loose page size which set by user and use default value:
> {{qry = ctx.queries().createScanQuery(p, transformer, scanQry.getPartition(),
> isKeepBinary)}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
