You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Andrey Mashenkov (Jira)" <ji...@apache.org> on 2025/12/05 08:47:00 UTC

[jira] [Updated] (IGNITE-26846) Get rid of InternalTable test methods.

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

Andrey Mashenkov updated IGNITE-26846:
--------------------------------------
    Priority: Minor  (was: Major)

> Get rid of InternalTable test methods.
> --------------------------------------
>
>                 Key: IGNITE-26846
>                 URL: https://issues.apache.org/jira/browse/IGNITE-26846
>             Project: Ignite
>          Issue Type: Improvement
>          Components: tables ai3
>            Reporter: Andrey Mashenkov
>            Assignee: Egor Kuts
>            Priority: Minor
>              Labels: ignite-3
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> InternalTable interface contains few methods that are used in tests only. 
> These methods accepts/starts transaction object and enlists touched rows. Seems, they were designed to scan table for remote partitions as well.
> They are not used in SQL, because SQL manage transaction on higher-level and performs only local partition scans.
> Let's provide public API if it make sense, either drop them otherwise.



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