[ 
https://issues.apache.org/jira/browse/IGNITE-4540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821738#comment-15821738
 ] 

Andrew Mashenkov commented on IGNITE-4540:
------------------------------------------

I've decouple GridQueryProcessor and GridIndexingManager. So, they can be 
configured independently.
Entry events for all caches (except system caches) pass to IndexingSPI if 
IndexingSpi is configured. Before this fix, IndexingSPI can process events for 
only caches which has IndexingTypes\QueryEntities  configured, e.i. entries 
that allowed to be indexed by default H2Indexing. 

> Ability to disable default H2 Indexing.
> ---------------------------------------
>
>                 Key: IGNITE-4540
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4540
>             Project: Ignite
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 1.8
>            Reporter: Andrew Mashenkov
>            Assignee: Andrew Mashenkov
>            Priority: Minor
>             Fix For: 1.9
>
>
> It is impossible for now to use IndexingSPI without H2Indexing due to next 
> reasons:
> - H2Indexing always starts if IgniteH2Indexing class found in classpath.
> - if IndexingTypes are set and IndexingSPI is configured, then both 
> IndexingSPI and H2Indexing is used. If IndexingTypes is not set, then both 
> indexers are disabled.
> We need to add an option that force disabling H2IndexingSpi. 
> It look like the only workaround for now is remove ignite-indexing jar from 
> classpath.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to