[
https://issues.apache.org/jira/browse/IGNITE-18501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-18501:
---------------------------------------
Description:
We still using QueryProcessor#queryAsync method in our test framework
(QueryChecker).
As of now there are some test which fails during migrate to
{code:java}
QueryProcessor#querySingleAsync{code}
As example such test can be used
org.apache.ignite.internal.sql.engine.ItSecondaryIndexTest#testSelectWithRanges
Let's investigate the reason, fix it and migrate QueryChecker to
querySingleAsync method.
was:
We still using QueryProcessor#querySingleAsync method in our test framework
(QueryChecker).
As of now there are some test which fails during migrate to
{code:java}
QueryProcessor#queryAsync{code}
As example such test can be used
org.apache.ignite.internal.sql.engine.ItSecondaryIndexTest#testSelectWithRanges
Let's investigate the reason, fix it and migrate QueryChecker to queryAsync
method.
> Sql. QueryChecker still use deprecated QueryProcessor#queryAsync method
> -----------------------------------------------------------------------
>
> Key: IGNITE-18501
> URL: https://issues.apache.org/jira/browse/IGNITE-18501
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Reporter: Yury Gerzhedovich
> Assignee: Yury Gerzhedovich
> Priority: Major
> Labels: ignite-3
>
> We still using QueryProcessor#queryAsync method in our test framework
> (QueryChecker).
> As of now there are some test which fails during migrate to
> {code:java}
> QueryProcessor#querySingleAsync{code}
>
> As example such test can be used
> org.apache.ignite.internal.sql.engine.ItSecondaryIndexTest#testSelectWithRanges
> Let's investigate the reason, fix it and migrate QueryChecker to
> querySingleAsync method.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
