[
https://issues.apache.org/jira/browse/IGNITE-26913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov updated IGNITE-26913:
--------------------------------------
Fix Version/s: 3.2
> Sql. InternalTable interface refactoring.
> -----------------------------------------
>
> Key: IGNITE-26913
> URL: https://issues.apache.org/jira/browse/IGNITE-26913
> Project: Ignite
> Issue Type: Improvement
> Components: sql ai3
> Affects Versions: 3.2
> Reporter: Andrey Mashenkov
> Assignee: Andrey Mashenkov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.2
>
>
> InternalTable interface contains a bunch of similar `scan()` and `lookup()`
> methods that are used mostly by SQL.
> These method discloses TX stuff and maybe other parameters, which are not
> related to the operation itself, but have impact on the execution flow.
> Let't pack TX and security stuff into an OperationContext holder-class.
> Also, we can do the same with the index search bounds.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
