You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@htrace.apache.org by "Nisala Mendis (JIRA)" <ji...@apache.org> on 2016/07/17 21:12:20 UTC
[jira] [Commented] (HTRACE-362) Apache KUDU Span receiver
implementation for Apache HTrace
[ https://issues.apache.org/jira/browse/HTRACE-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381519#comment-15381519 ]
Nisala Mendis commented on HTRACE-362:
--------------------------------------
Hi Colin,
I have update pr s for HTRACE-362 and HTRACE-363 in [1] and [2] . With related to 362, I have added all changes as you requested except for schema, I had a problem in this case where I needed to handle list of timeline annotations per span and storying those multiple annotations associated with a single span in a schema. Please let me know your suggestion on this. Except that I have fully tested the kudu span receiver code and created automated unit test cases re-using kudu mini cluster test utilities. With related to 363, I have executed the unit tests as batch and found out no issues with failing tests.
[1] https://github.com/apache/incubator-htrace/pull/11/files
[2] https://github.com/apache/incubator-htrace/pull/9/files
Regards
Nisala
> 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, 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)