[jira] [Commented] (IGNITE-12908) Confusing check for presence of SqlViewExporterSpi class in classpath during initialization

[Ignite TC Bot (Jira)]

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

Ignite TC Bot commented on IGNITE-12908:
----------------------------------------

{panel:title=Branch: [pull/7695/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5240833&buildTypeId=IgniteTests24Java8_RunAll]

> Confusing check for presence of SqlViewExporterSpi class in classpath during 
> initialization
> -------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-12908
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12908
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Andrey N. Gura
>            Assignee: Mikhail Petrov
>            Priority: Minor
>              Labels: IEP-35
>             Fix For: 2.8.1
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> {{IgnitionEx.initializeDefaultSpi()}} method checks for presence of 
> {{SqlViewExporterSpi}} class in classpath whilst actual intention is to check 
> for presence of indexing in classpath. It could be done just using 
> {{IgniteComponentType.INDEXING.inClassPath()}} method.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)