[
https://issues.apache.org/jira/browse/IGNITE-13056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308554#comment-17308554
]
Taras Ledkov commented on IGNITE-13056:
---------------------------------------
[~timonin.maksim], the patch is OK with me. Please fix minors (typos and
style): i left the comments at the PR.
I guess we have to wait the community's decision about the
[MVCC|http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Patch-completely-breaks-MVCC-td51779.html]
before merge the patch.
> SchemaManager refactoring
> -------------------------
>
> Key: IGNITE-13056
> URL: https://issues.apache.org/jira/browse/IGNITE-13056
> Project: Ignite
> Issue Type: New Feature
> Components: sql
> Affects Versions: 2.8
> Reporter: Nikolay Izhikov
> Assignee: Maksim Timonin
> Priority: Major
> Labels: IEP-49, calcite
> Time Spent: 11.5h
> Remaining Estimate: 0h
>
> Since Ignite wants to leverage from several SQL engines we need to make work
> with index independent from the used SQL engine.
> We also should consider moving all machinery related to an index to the core
> module to make it available from any module that wants to use it.
> Requirements so far:
> * Ability to track indexes in several engines
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
