[
https://issues.apache.org/jira/browse/IGNITE-10721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16750128#comment-16750128
]
Alexey Kosenchuk commented on IGNITE-10721:
-------------------------------------------
[~isapego]
Ok, if it's just a 128-bit number, why it can not be simply encoded as 16 bytes
array (LSB or MSB - should be specified)?
What is a purpose/benefit to encode it as two 64-bit numbers in the protocol?
> Documentation: Fix UUID thin client format description
> ------------------------------------------------------
>
> Key: IGNITE-10721
> URL: https://issues.apache.org/jira/browse/IGNITE-10721
> Project: Ignite
> Issue Type: Task
> Components: documentation, thin client
> Reporter: Igor Sapego
> Assignee: Igor Sapego
> Priority: Major
> Fix For: 2.8
>
>
> UUID thin client format description [1] need to be fixed. The actual format
> of the UUID should be two longs, not a single 128-bit value. Two longs
> written in little-endian are not equal to one 128-bit number.
> [1] -
> https://apacheignite.readme.io/docs/binary-client-protocol-data-format#section-uuid-guid-
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
