You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2026/04/03 13:02:00 UTC

[jira] [Assigned] (IGNITE-28452) Sql. Cleanup ScannableTable interface

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

Konstantin Orlov reassigned IGNITE-28452:
-----------------------------------------

    Assignee: Konstantin Orlov

> Sql. Cleanup ScannableTable interface
> -------------------------------------
>
>                 Key: IGNITE-28452
>                 URL: https://issues.apache.org/jira/browse/IGNITE-28452
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql ai3
>            Reporter: Konstantin Orlov
>            Assignee: Konstantin Orlov
>            Priority: Major
>              Labels: ignite-3
>
> Currently, index-related methods on {{ScannableTable}} interface accepts list of columns as input:
> {code}
>     <RowT> Publisher<RowT> indexRangeScan(
>             ExecutionContext<RowT> ctx,
>             PartitionWithConsistencyToken partWithConsistencyToken,
>             RowFactory<RowT> rowFactory,
>             int indexId,
>             List<String> columns,
>             @Nullable RangeCondition<RowT> cond,
>             int @Nullable [] requiredColumns
>     );
> {code}
> Internally, we use only size of the list in order to compose proper search key (either {{BinaryTuplePrefix}} or just {{BinaryTuple}}). We need to encapsulate all necessary meta within {{ScannableTable}} and clean up interface.



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