[ 
https://issues.apache.org/jira/browse/IGNITE-21094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Pereslegin updated IGNITE-21094:
--------------------------------------
    Description: 
At the moment we have two methods for executing queries:
{{querySingleAsync}} for executing single-statement query
{{queryScriptAsync}} for executing multi-statement query.

These methods have an identical signature, so they can be easily combined into 
one.

The simple solution will be to keep, for example, `queryAsync` as a single 
entry point.
It seems that, internally, we can figure out how to execute this query, 
depending on the query execution property {{ALLOWED_QUERY_TYPES}}. For example, 
{{querySingleAsync}} does not allow the TX_CONTROL type.


  was:
At the moment we have two methods for executing queries:
{{querySingleAsync}} for executing single-statement query
{{queryScriptAsync}} for executing multi-statement query.

These methods have an identical signature, so they can be easily combined into 
one.

The simple solution will be to keep, for example, `queryAsync` as a single 
entry point.
It seems that, internally, we can figure out how to execute this query, 
depending on the query execution property {{ALLOWED_QUERY_TYPES}}. 
{{querySingleAsync}} does not allow the TX_CONTROL type.



> Sql. Combine query execution methods (single/script) in QueryProcessor.
> -----------------------------------------------------------------------
>
>                 Key: IGNITE-21094
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21094
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Pavel Pereslegin
>            Priority: Major
>              Labels: ignite-3
>
> At the moment we have two methods for executing queries:
> {{querySingleAsync}} for executing single-statement query
> {{queryScriptAsync}} for executing multi-statement query.
> These methods have an identical signature, so they can be easily combined 
> into one.
> The simple solution will be to keep, for example, `queryAsync` as a single 
> entry point.
> It seems that, internally, we can figure out how to execute this query, 
> depending on the query execution property {{ALLOWED_QUERY_TYPES}}. For 
> example, {{querySingleAsync}} does not allow the TX_CONTROL type.



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

Reply via email to