[
https://issues.apache.org/jira/browse/IGNITE-19818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738245#comment-17738245
]
Ignite TC Bot commented on IGNITE-19818:
----------------------------------------
{panel:title=Branch: [pull/10804/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10804/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Calcite SQL{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7231903]]
* {color:#013220}IgniteCalciteTestSuite:
ServerStatisticsIntegrationTest.testSizeIntOverflow - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7231984&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine. Query planning failed when cache size is too big
> ----------------------------------------------------------------
>
> Key: IGNITE-19818
> URL: https://issues.apache.org/jira/browse/IGNITE-19818
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: ise
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We use cache size as estimation for row count while planning, but use
> {{cache.size()}} method, that returns int value. But if cache size is more
> than {{Integer.MAX_VALUE}} we get an wrong size or even negative sometimes,
> which cause assertion errors during planning.
> We should fix it to {{cache.sizeLong()}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
