[
https://issues.apache.org/jira/browse/HTRACE-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15411089#comment-15411089
]
Nisala Mendis commented on HTRACE-362:
--------------------------------------
Hi Colin,
Herewith attaching patch HTRACE-362.003.patch. You could compare changes from
here. [1]
KuduClientConfiguration - Changes are done to make all fields final.
KuduReceiverConstants - Removed "htrace." prefixes from config keys. Made
constants package-private.
Protobuf dependency - This is now removed. Please let me know if you have
concerns over the current schema. All span and time line annotation fields are
in their respective types in kudu tables. We now store spans and their
associated timeline annotations in two separate tables.
Cloudera repos in pom.xml. - Seems like kudu db client artifacts are not
available in Apache maven central repositories. Please advice how we can
proceed with this.
[1]
https://github.com/apache/incubator-htrace/pull/11/commits/a6ca3ccf8007f41a112baf98328b9311b7148e7b
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, HTRACE-362.002.patch,
> HTRACE-362.003.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)
