[
https://issues.apache.org/jira/browse/HTRACE-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648094#comment-14648094
]
Colin Patrick McCabe commented on HTRACE-209:
---------------------------------------------
bq. To summarize, I'm fine if it opaque random bits but would favor type 4
UUID. If the former, lets remove the hyphen separators that make it look like a
UUID. If the latter, and we receive an illegal type-4 format UUID, we just eat
it.
That's a fair point. Let's just go with a git-style big 128-bit hex number.
I don't want to chop off any bits because it would ruin our compatibility with
existing wire protocols, and with zipkin (both of which expect us to be able to
pass through 128 bits).
> Make span ID 128 bit to avoid collisions
> ----------------------------------------
>
> Key: HTRACE-209
> URL: https://issues.apache.org/jira/browse/HTRACE-209
> Project: HTrace
> Issue Type: Sub-task
> Affects Versions: 4.0
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Attachments: HTRACE-209.001.patch, HTRACE-209.002.patch,
> HTRACE-209.004.patch, HTRACE-209.005.patch
>
>
> Make span ID 128 bit to avoid collisions in htrace 4.x
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
