[
https://issues.apache.org/jira/browse/IGNITE-19726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Zhuravkov updated IGNITE-19726:
--------------------------------------
Description:
When https://issues.apache.org/jira/browse/IGNITE-19587 is complete, it is
possible to move execution related index methods to ScanableTable, thus
removing remaining execution related objects from IgniteTableImpl:
- IndexScanNode: index scans/looks should be performed via ScanableTable APIs.
- StorageNode.convertPublisher should be moved to ScanableTableImpl.
was:
When https://issues.apache.org/jira/browse/IGNITE-19587 is complete, it is
possible to move execution related index methods to ScanableTable, thus
removing remaining execution related methods from IgniteTableImpl:
- IndexScanNode: index scans/looks should be performed via ScanableTable APIs.
- StorageNode.convertPublisher should be moved to ScanableTableImpl.
> Sql. Migrate index operations to ScanableTable.
> -----------------------------------------------
>
> Key: IGNITE-19726
> URL: https://issues.apache.org/jira/browse/IGNITE-19726
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 3.0.0-beta2
> Reporter: Maksim Zhuravkov
> Assignee: Maksim Zhuravkov
> Priority: Minor
> Labels: ignite-3
>
> When https://issues.apache.org/jira/browse/IGNITE-19587 is complete, it is
> possible to move execution related index methods to ScanableTable, thus
> removing remaining execution related objects from IgniteTableImpl:
> - IndexScanNode: index scans/looks should be performed via ScanableTable APIs.
> - StorageNode.convertPublisher should be moved to ScanableTableImpl.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
