[jira] [Commented] (IGNITE-4540) Ability to disable default H2 Indexing.

["Valentin Kulichenko (JIRA)" <ji...@apache.org>]

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

Valentin Kulichenko commented on IGNITE-4540:
---------------------------------------------

[~amashenkov], I don't think we need to add any new options for this. Current problem is that we go though two different checks before calling {{IndexingSpi.store(..)}}: {{GridCacheQueryManager.enabled()}} and then {{GridIndexingManager.enabled()}}. When custom {{IndexingSpi}} is used, the second one is true, but the first one is false. We need to fix the logic and make sure everything is working properly in this case.

> 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
>            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)