[ 
https://issues.apache.org/jira/browse/IGNITE-20006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748329#comment-17748329
 ] 

Ignite TC Bot commented on IGNITE-20006:
----------------------------------------

{panel:title=Branch: [pull/10852/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10852/head] Base: [master] : No new tests 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All* 
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7265886&buildTypeId=IgniteTests24Java8_RunAll]

> Calcite engine. Make table/index scan iterators yieldable 
> ----------------------------------------------------------
>
>                 Key: IGNITE-20006
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20006
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Aleksey Plekhanov
>            Assignee: Aleksey Plekhanov
>            Priority: Major
>              Labels: calcite, ise
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Currently, index/table iterators can scan unpredictable count of cache 
> entries during one {{hasNext()}}/{{next()}} call. These iterators contain 
> filter, which applyed to each entry and row produced only for entries that 
> satisfy filter. If filter contains "always false" rule, one {{hasNext()}} 
> call may scan entiry table uninterruptably, without timeouts and yields to 
> make another queries do their job. We should fix this behaviour.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to