[
https://issues.apache.org/jira/browse/HTRACE-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259479#comment-14259479
]
Colin Patrick McCabe commented on HTRACE-25:
--------------------------------------------
Thanks for looking at this. I think this approach is not what we need, though,
for a few reasons.
We should keep all the logic for interacting with hbase in htrace-hbase, rather
than spreading it across modules. If you want to send spans to htrace, you can
simply use htrace-hbase, right? In general, what we want is a way for
htrace-flume to simply use the standard htrace-core API to re-send spans to any
span receiver.
An architecture like this:
{code}
htraced
^
|
htrace-flume --> htrace-core API --> htrace-hbase <-> hbase
|
V
other span receivers
{code}
This will be a lot less code, and a lot more flexible. It means we can use any
span receiver.
> htrace-flume: add hbase sink support
> ------------------------------------
>
> Key: HTRACE-25
> URL: https://issues.apache.org/jira/browse/HTRACE-25
> Project: HTrace
> Issue Type: Improvement
> Reporter: Long Zhou
> Assignee: Long Zhou
> Attachments: htrace-25.001.patch
>
>
> To put spans collected by flume agent into hbase, we need to implement a
> customized HbaseEventSerializer that can convert flume events to hbase put
> requests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
