[
https://issues.apache.org/jira/browse/IGNITE-28719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18102417#comment-18102417
]
Ignite TC Bot commented on IGNITE-28719:
----------------------------------------
{panel:title=Branch: [pull/13438/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13438/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=9257729&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9257729
rerunBuildIds=none{color}
> Revise GridTopicMessage usage in messages
> -----------------------------------------
>
> Key: IGNITE-28719
> URL: https://issues.apache.org/jira/browse/IGNITE-28719
> Project: Ignite
> Issue Type: Task
> Reporter: Dmitry Werner
> Assignee: Dmitry Werner
> Priority: Minor
> Labels: IEP-132, ise, wire-format
> Fix For: 2.19
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently GridTopicMessage is used in 3 messages: GridIoMessage,
> GridDeploymentRequest, DataStreamerRequest.
> In GridDeploymentRequest and DataStreamerRequest, instead of passing an
> Object topic, an IgniteUuid could be used.
> This simplifies the code and also unifies the approach already implemented in
> GridEventStorageRequest.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
