I filed https://issues.apache.org/jira/browse/HTRACE-386 to take a look
at this.

best,


On Wed, Sep 14, 2016, at 12:43, Colin McCabe wrote:
> Oh yeah... I guess I should have included that :P
> 
> Thanks, Mike.
> 
> C.
> 
> 
> On Wed, Sep 14, 2016, at 12:42, Mike Drob wrote:
> > And in case you are unsure of where to find our JIRA instance - here is a
> > link!
> > 
> > https://issues.apache.org/jira/browse/HTRACE
> > 
> > On Wed, Sep 14, 2016 at 2:39 PM, Colin McCabe <cmcc...@apache.org> wrote:
> > 
> > > Hi Byung-Gon,
> > >
> > > Hmm.  The lack of an API for getting the current trace ID does look like
> > > an omission!  I think we should add this.  It shouldn't be too
> > > difficult.
> > >
> > > I would say, open a JIRA so we can take a look.
> > >
> > > best,
> > > Colin
> > >
> > > On Tue, Sep 13, 2016, at 14:57, Byung-Gon Chun wrote:
> > > > Hi,
> > > >
> > > > We've been using HTrace for Java. This really worked well. Thanks!
> > > >
> > > > We hope to trace C++ code with HTrace as well. But it looks like C++ 
> > > > does
> > > > not expose all the features we need (e.g., getting a span id). What's 
> > > > the
> > > > best way to approach this?
> > > >
> > > > Thanks.
> > > > Byung-Gon Chun
> > >

Reply via email to