[
https://issues.apache.org/jira/browse/IGNITE-27778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18067631#comment-18067631
]
Ignite TC Bot commented on IGNITE-27778:
----------------------------------------
{panel:title=Branch: [pull/12919/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/12919/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8950800&buildTypeId=IgniteTests24Java8_RunAll]
> Refactor of DiscoverySpiCustomMessage
> -------------------------------------
>
> Key: IGNITE-27778
> URL: https://issues.apache.org/jira/browse/IGNITE-27778
> Project: Ignite
> Issue Type: Task
> Reporter: Ilya Shishkov
> Assignee: Nikita Amelchev
> Priority: Major
> Labels: IEP-132, ise
> Fix For: 2.19
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> The interface should not be removed as it is a public API. After migrating to
> the new framework, Serializable can be removed to avoid supporting two types
> of serialization in messages.
> We need to revert DiscoverySpi#sendCustomEvent (to accept
> DiscoverySpiCustomMessage as before).
> Make the DiscoverySpiCustomMessage interface extend Message.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)