[
https://issues.apache.org/jira/browse/IGNITE-28374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18091750#comment-18091750
]
Ignite TC Bot commented on IGNITE-28374:
----------------------------------------
{panel:title=Branch: [pull/13225/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13225/head] Base: [master] : New Tests
(11)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Calcite SQL 3{color} [[tests
11|https://ci2.ignite.apache.org/viewLog.html?buildId=9138200]]
* {color:#013220}IgniteCalciteTestSuite3:
SelectByKeyFieldTest.testJavaObjCompositePkComparisonsWithTableScan -
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite3:
SelectByKeyFieldTest.testBinaryCompositePkComparisonsWithIdxScan - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite3:
SelectByKeyFieldTest.testJavaObjCompositePkComparisonsWithIdxScan -
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite3:
SelectByKeyFieldTest.testBinaryCompositePkComparisonsWithTableScan -
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite3:
SelectByKeyFieldTest.testResultsWithoutKeyTypeWithUnexpectedBOAsParam -
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite3:
SelectByKeyFieldTest.testResultsWithoutKeyTypeWithUnexpectedParam -
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite3:
SelectByKeyFieldTest.testCompositePkWithOrderByKeyTableScan - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite3:
SelectByKeyFieldTest.testCompositePkSearchByPartOfKeyTableScan - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite3:
SelectByKeyFieldTest.testResultsWithUnexpectedParam - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite3:
SelectByKeyFieldTest.testCompositePkWithOrderByKeyIdxScan - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite3:
SelectByKeyFieldTest.testCompositePkSearchByPartOfKeyIdxScan - PASSED{color}
... and 0 new tests
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9138215&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9138215
rerunBuildIds=9152659{color}
> Calcite. Fix SQL select by _key for a composite pk for key class.
> -----------------------------------------------------------------
>
> Key: IGNITE-28374
> URL: https://issues.apache.org/jira/browse/IGNITE-28374
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.18
> Reporter: Kirill Tkalenko
> Assignee: Evgeny Stanilovsky
> Priority: Major
> Labels: ignite-2, ise
> Time Spent: 40m
> Remaining Estimate: 0h
>
> IGNITE-28331 successfully fixed selects with "_KEY" for composite primary
> key, but it still doesn't resolve the issue when the key class is passed as a
> parameter.
> See todo and issue needs to be fixed in this ticket.
> Research result:
> If convert a POJO to a BinaryObject for the index search boundary, then after
> retrieving rows from the index, the Calcite filter from the query is applied
> within the iterator, comparing the key retrieved from the index with the
> argument passed to the query. This results in a comparison of the
> BinaryObject with the POJO, which cannot be equal, and therefore such rows
> are skipped.
> See
> *org.apache.ignite.internal.processors.query.calcite.exec.rel.ScanTableRowNode#processNextRow*.
> This problem can be fixed, for example, by converting a POJO to a
> BinaryObject when receiving them as a query argument in method
> *org.apache.ignite.internal.processors.query.calcite.exec.ExecutionContext#getParameter*.
> However, this could break the ability to pass POJO to user-defined
> functions. Perhaps there is a simpler or more elegant solution.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
