[
https://issues.apache.org/jira/browse/IGNITE-17069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545391#comment-17545391
]
Ignite TC Bot commented on IGNITE-17069:
----------------------------------------
{panel:title=Branch: [pull/10060/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10060/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Calcite SQL{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6602490]]
* {color:#013220}IgniteCalciteTestSuite:
IndexScanlIntegrationTest.testSegmentedIndexes - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6602491&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine. Support segmented indexes
> -----------------------------------------
>
> Key: IGNITE-17069
> URL: https://issues.apache.org/jira/browse/IGNITE-17069
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: calcite, calcite2-required
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currentrly we silently return the wrong result if index is segmented (query
> parallelism is set for table). While query parallelism is not supported (see
> IGNITE-13027) by the Calcite query engine, we should at least process all
> segments of the index during index scan.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
