[
https://issues.apache.org/jira/browse/HTRACE-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437201#comment-15437201
]
Colin P. McCabe commented on HTRACE-362:
----------------------------------------
The data model of HTrace changed between HTrace 3 and HTrace 4. Process ID was
replaced with Tracer ID, in order to distinguish between spans generated by
different libraries in the same process. The Span ID was widened to 128 bits
to avoid the possibility of collisions. Trace ID went away.
HBaseSpanReceiver still needs to be updated to take into account these changes.
We have been more focused on HBase as a thing to be traced rather than as a
trace sink, so these changes haven't been done yet. See HTRACE-225 for an
example of one of the things that has to be done to fix HBaseSpanReceiver.
This is one reason why I suggested that you look at LocalFileSpanReceiver and
HTracedSpanReceiver rather than HBaseSpanReceiver.
Let's get the data model right here.
bq. Please check span viewer classes as well.
This JIRA is titled "Kudu Span Receiver implementation," so let's focus on the
span receiver. We should have separate JIRAs for the UI.
bq. If you can point to kudu binaries you can excute unit tests which are
currently being disabled.
We will need to be sure that our unit tests can run on Jenkins-- that will
probably involve adding Kudu to the Docker image.
> Apache KUDU Span receiver implementation for Apache HTrace
> ----------------------------------------------------------
>
> Key: HTRACE-362
> URL: https://issues.apache.org/jira/browse/HTRACE-362
> Project: HTrace
> Issue Type: Bug
> Reporter: Nisala Mendis
> Assignee: Nisala Mendis
> Attachments: HTRACE-362.001.patch, HTRACE-362.002.patch,
> HTRACE-362.003.patch, HTRACE-362.004.patch, HTRACE-362.005.patch,
> kudu_receiver.patch, kudu_span_receiver_basic_design.pdf
>
>
> Implementation should be carried two components as span receiver that writes
> kudu back end and span viewer to view written span/traces.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
