[
https://issues.apache.org/jira/browse/IGNITE-10721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16723904#comment-16723904
]
Alexey Kosenchuk commented on IGNITE-10721:
-------------------------------------------
In this case, the content/meaning of these two longs should be clarified.
Eg. if the supported UUID is RFC-4122 UUID, then how it's fields (time_low,
time_mid,...) should be located in that two longs.
> 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)
