[
https://issues.apache.org/jira/browse/IGNITE-28719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Werner updated IGNITE-28719:
-----------------------------------
Description:
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.
was:
Currently, the GridTopic enum contains internal classes T1–T4, T6, and T8, each
of which includes a GridTopic field along with other fields.
It is proposed to extract these tuples from the GridTopic and convert them into
messages.
For example, we can create:
- GridTopicAbstractMessage — a message that stores only the enum value;
- GridTopicMessageTuple1 — a message that stores the enum value plus an id.
This approach will simplify the GridTopic enum: it will contain only enum
values, and nothing more.
> 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)
