[
https://issues.apache.org/jira/browse/IGNITE-9386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408723#comment-17408723
]
Ignite TC Bot commented on IGNITE-9386:
---------------------------------------
{panel:title=Branch: [pull/9362/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9362/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6159835&buildTypeId=IgniteTests24Java8_RunAll]
> control.sh --tx can produce confusing results when limit is set to small value
> ------------------------------------------------------------------------------
>
> Key: IGNITE-9386
> URL: https://issues.apache.org/jira/browse/IGNITE-9386
> Project: Ignite
> Issue Type: Improvement
> Components: control.sh
> Affects Versions: 2.10
> Reporter: Alexey Scherbakov
> Assignee: Rodion Smolnikov
> Priority: Major
> Fix For: 2.11
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This is happening because currently the limit is applied to primary and
> backup transactions, which breaks output post-filtering (removal of primary
> and backup transactions from output if near is present).
> Possible solution: apply limit only to near valid transactions. If some txs
> have no near part (broken tx topology), they should be always visible in
> output, probably with special "broken" marking.
> Best way to achieve this - implement tx paging on client side (using
> continuous mapping)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
