[
https://issues.apache.org/jira/browse/IGNITE-26635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov updated IGNITE-26635:
--------------------------------------
Ignite Flags: (was: Docs Required,Release Notes Required)
> Sql. Decouple ExpressionExecution part from ExecutionContext
> ------------------------------------------------------------
>
> Key: IGNITE-26635
> URL: https://issues.apache.org/jira/browse/IGNITE-26635
> Project: Ignite
> Issue Type: Improvement
> Components: sql ai3
> Affects Versions: 3.1
> Reporter: Konstantin Orlov
> Assignee: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As for now, every sql expression interface requires {{ExecutionContext}} as
> input. The problem is that {{ExecutionContext}} contains not only context
> required for expression evaluation, but also a lot of sql-related stuff like
> fragment information, executor, expression factory, etc. To simplify
> decoupling of expression execution engine, we should derive minimal context
> required for expression execution.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
