[
https://issues.apache.org/jira/browse/IGNITE-13164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-13164:
---------------------------------------
Description:
Currently, each node id in thin client execute compute task request is written
using 17 bytes (1 byte for type id and 16 bytes for UUID raw data). Since we
don't need information about type id and node id can't be null we can write
only UUID raw data as now implemented for service invoke request.
Compute functionality is not released yet, so format can be changed without
compatibility issues.
was:Currently, each node id in thin client execute compute task request is
written using 17 bytes (1 byte for type id and 16 bytes for UUID raw data).
Since we don't need information about type id and node id can't be null we can
write only UUID raw data as now implemented for service invoke request.
> Thin client: Fix nodeIds format for execute compute tasks request
> ------------------------------------------------------------------
>
> Key: IGNITE-13164
> URL: https://issues.apache.org/jira/browse/IGNITE-13164
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, each node id in thin client execute compute task request is
> written using 17 bytes (1 byte for type id and 16 bytes for UUID raw data).
> Since we don't need information about type id and node id can't be null we
> can write only UUID raw data as now implemented for service invoke request.
> Compute functionality is not released yet, so format can be changed without
> compatibility issues.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
