[
https://issues.apache.org/jira/browse/HTRACE-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15280637#comment-15280637
]
Todd Lipcon commented on HTRACE-362:
------------------------------------
bq. A lot of projects find it difficult or impossible to actually have a stable
C++ ABI. It's very easy to end up with two different C++ library versions that
look compatible but which crash when you use code linked against one with code
linked against another.
Right, we're aware of these issues and do our best to avoid problems here.
The suggestion is that rather than having a Kudu C API, you can have a
kudu-htrace C API. eg the APIs can be things like:
{code}
extern void submit_trace(const char* trace_thrift_obj, int len);
{code}
rather than trying to actually expose all the complexity of Kudu.
> 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: 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)
