[
https://issues.apache.org/jira/browse/IGNITE-17061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasiliy Sisko updated IGNITE-17061:
-----------------------------------
Description:
When I configure different deployment SPI for different nodes I receive the
next message
_Remote SPI with the same name is not configured_
when I expect to get the message
_Remote SPI with the same name is of different type_
I got it because *org.apache.ignite.spi.IgniteSpiAdapter* use
*U.getSimpleName(getClass())* for SPI name generation in
org.apache.ignite.spi.IgniteSpiAdapter#IgniteSpiAdapter`, that looks like a
mistake.
was:
When I configure different deployment SPI for different nodes I receive the
next message
Remote SPI with the same name is not configured
when I expect to get the message
Remote SPI with the same name is of different type
I got it because *org.apache.ignite.spi.IgniteSpiAdapter* use
*U.getSimpleName(getClass())* for SPI name generation in
org.apache.ignite.spi.IgniteSpiAdapter#IgniteSpiAdapter`, that looks like a
mistake.
> Invalid detection of SPI on configuration validation.
> -----------------------------------------------------
>
> Key: IGNITE-17061
> URL: https://issues.apache.org/jira/browse/IGNITE-17061
> Project: Ignite
> Issue Type: Bug
> Components: general
> Affects Versions: 2.13
> Reporter: Vasiliy Sisko
> Priority: Major
>
> When I configure different deployment SPI for different nodes I receive the
> next message
> _Remote SPI with the same name is not configured_
> when I expect to get the message
> _Remote SPI with the same name is of different type_
> I got it because *org.apache.ignite.spi.IgniteSpiAdapter* use
> *U.getSimpleName(getClass())* for SPI name generation in
> org.apache.ignite.spi.IgniteSpiAdapter#IgniteSpiAdapter`, that looks like a
> mistake.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
