[
https://issues.apache.org/jira/browse/IGNITE-10721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738047#comment-16738047
]
Igor Sapego commented on IGNITE-10721:
--------------------------------------
[~alexey.kosenchuk],
The documentation was invalid, so it should be fixed in current version (and
probably in all previous versions as well).
UUID is 128-bit number which is stated in its description. RFC 4122 tells that
as well. In our protocol we do not define a format of this number, as I don't
see how user may benefit from such a definition as all parts of the system only
treat UUID as a large number. The details on how such number is generated is
not really relevant for the system.
Now when we sat that UUID is just a 128-bit number "64 most significant bits of
UUID" and "64 least significant bits of UUID" should be quite obvious. Do you
have proposals on how can we improve description here?
> 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)
