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

Konstantin Orlov updated IGNITE-25092:
--------------------------------------
    Description: 
Currently, for statements of script Running Queries view returns query string 
which is result of {{qlNode.toString()}}. The problem is default {{toString()}} 
returns unparsed AST in {{Ansi}} dialect which is incompatible with the one we 
use.

It would be nice to have query string in the original form, i.e. the same form 
it specified in the script, but we need to make sure reassembling of original 
query won't affect performance. Otherwise we should unparse AST in our dialect 
to at least make it possible to execute queries derived from Running Queries 
view.

  was:
Currently, for statements of script Running Queries view returns query string 
which is result {{qlNode.toString()}}. The problem is default {{toString()}} 
returns unparsed AST in {{Ansi}} dialect which is unsupported with the one we 
use.

It would be nice to have query string in the original form, i.e. the same form 
it specified in the script, but we need to make sure reassembling of original 
query won't affect performance. Otherwise we should unparse AST in our dialect 
to at least make it possible to execute queries derived from Running Queries 
view.


> Sql. Running queries view should return query string in valid format 
> ---------------------------------------------------------------------
>
>                 Key: IGNITE-25092
>                 URL: https://issues.apache.org/jira/browse/IGNITE-25092
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Konstantin Orlov
>            Assignee: Konstantin Orlov
>            Priority: Major
>              Labels: ignite-3
>
> Currently, for statements of script Running Queries view returns query string 
> which is result of {{qlNode.toString()}}. The problem is default 
> {{toString()}} returns unparsed AST in {{Ansi}} dialect which is incompatible 
> with the one we use.
> It would be nice to have query string in the original form, i.e. the same 
> form it specified in the script, but we need to make sure reassembling of 
> original query won't affect performance. Otherwise we should unparse AST in 
> our dialect to at least make it possible to execute queries derived from 
> Running Queries view.



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

Reply via email to