[
https://issues.apache.org/jira/browse/IMPALA-14332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18051004#comment-18051004
]
Nikhil Bhatia commented on IMPALA-14332:
----------------------------------------
Hey [~jasonmfehr] I would like to work on this issue, but otel accepts trace_id
as a 32 character hex string and not a uuid, but the X-Request-id is a uuid, so
to use the X-Request-id as the trace_id we either need to have a custom id
generator or strip the hyphens from the X-Request-id and use it as trace_id.
> Set OpenTelemetry TraceId to X-Request-Id Header Value
> ------------------------------------------------------
>
> Key: IMPALA-14332
> URL: https://issues.apache.org/jira/browse/IMPALA-14332
> Project: IMPALA
> Issue Type: Improvement
> Affects Versions: Impala 5.0.0
> Reporter: Jason Fehr
> Priority: Critical
>
> Currently the OpenTelemetry traces are created with a random trace id. If
> the "X-Request-Id" HTTP header is specified, set the trace id equal to the
> value of this header.
> Note: Impala shell includes the iteration count along with the request id
> guid. For example: "x-request-id=18bb03c8-7de6-11f0-9112-8b736586fd91-8".
> The iteration count will have to be removed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
