On Wed, Mar 14, 2018, 2:26 PM Billie Rinaldi
wrote:
> In the active thread "[VOTE] Retire HTrace from Incubation" Christopher
> Tubbs brought up the idea to make HTrace a subproject of an existing TLP.
This would mitigate the issues of the community being inactive and
t; >
> > > On Thu, Mar 8, 2018 at 4:52 PM Todd Lipcon <t...@cloudera.com> wrote:
> > >
> > > > On Thu, Mar 8, 2018 at 1:38 PM, Mike Drob <md...@apache.org> wrote:
> > > >
> > > > > +1 to ret
+1 to retire.
This is painful because I've spent a lot of time on this personally, and I
do think there is value, but not if nobody picks it up.
Christopher,
HTrace did not originate from Accumulo's cloudtrace effort. It spun out of
HDFS's efforts.
They were two separate things, where
Is it time to close up shop, folks? Zero activity in the last three months.
Stack - you still want more time?
On Thu, Mar 1, 2018 at 3:20 PM, wrote:
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial
Hi folks,
Want to pull this conversation back into people's minds to summarize and
reposit some questions.
It looks like there is consensus that 1) HTrace is generally useful but 2)
needs to refocus on more specific use cases rather than trying to be a
general purpose tool and 3) suffers from
+1 Stack
On Thu, Sep 7, 2017 at 4:44 PM, Stack wrote:
> Report is due. How is this? I'd like to put it up today since we are late
> already.
> Thanks,
> St.Ack
>
>
>
>
>
> HTrace
>
> HTrace is a tracing framework intended for use with distributed systems
> written in java.
>
>
Hi folks,
Want to bring up a potentially uncofortable topic for some. Is it time to
retire/attic the project?
We've seen a minimal amount of activity in the past year. The last release
had two bug fixes, and had been pending for several months before somebody
reminded me to push the artifacts to
t; > * built hadoop trunk against htrace-4.3.0-incubating.
> > > * verified that spans in HDFS works by HTracedSpanReceiver and htraced.
> > >
> > > Thanks,
> > > Masatake Iwasaki
> > >
> > >
> > > On 5/17/17 05:40, Mike Drob wrote:
Hi Devs,
Please consider the following release candidate for Apache HTrace
4.3.0-incubating!
http://people.apache.org/~mdrob/htrace-4.3.0-incubating-rc3/
The jars have been staged here:
https://repository.apache.org/content/repositories/orgapachehtrace-1029
There's a few minor fixes in this
I was able to update the htrace-htraced pom to use project.version, and
updated the hard coded string in CMakeLists.txt
I also filed HTRACE-397 to follow up on automating the CMakeLists change
every release.
Mike
On Mon, May 15, 2017 at 3:08 PM, Mike Drob <md...@apache.org> wrote:
> V
m.xml
> > * htrace-c/src/CMakeLists.txt
> >
> > cheers,
> > Colin
> >
> > On Mon, May 8, 2017, at 13:46, Mike Drob wrote:
> > > Hi Devs,
> > >
> > > Based on recent mailing list discussions, I've posted the first release
> > >
Hi Devs,
Based on recent mailing list discussions, I've posted the first release
candidate here: (rc0 had to be discarded due to an error on my part)
http://people.apache.org/~mdrob/htrace-4.3.0-incubating-rc1/
The jars have been staged here:
Had a chance to look at this in more detail. From the Java side we should
be safe to do 4.2.1. From the C side... I don't know what kind of
guarantees we offer there. Looks like addition of APIs, but I don't know
what C communities and users expect.
Colin and Masatake - since you were involved in
I can make time for running through the release next week. Any unresolved
JIRA issues will be bulk moved to 4.4 on Monday with this plan.
I'm assuming somebody had already done the check on whether this needs to
be a full 4.3 or can sneak in as a 4.2.1? Seem like we have a chance to not
increment
bit.
>>
>> I did encounter https://issues.apache.org/jira/browse/HTRACE-387 when
>> doing a quick test on this release. It's an existing bug, so I don't
>> think it merits a new R But if we do do a new RC, it would be nice.
>>
>> +1
>>
>> b
HTrace devs,
I've posted the first release candidate here:
http://people.apache.org/~mdrob/htrace-4.2.0-incubating-rc0/
Signed by my key, available here:
http://pgp.mit.edu/pks/lookup?op=vindex=0x3E48C0C6EF362B9E
The jars have been staged
Hey folks,
I've run into an issue where when I am building htrace the process gets
stuck creating a dep-reduced pom for htrace-hbase module over and over
again. I'm not sure which plugin is even asking for this pom file, or what
it gets used for/how it is generated. If anybody has seen anything
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 wrote:
> Hi Byung-Gon,
>
> Hmm. The lack of an API for getting the current trace ID does look like
>
I haven't found a great single source, but here is my method for using them.
First I look at
https://github.com/apache/incubator-htrace/blob/master/htrace-core4/src/main/java/org/apache/htrace/core/Tracer.java#L40-L41
to see the main properties.
Then, if I configure for example the
> No it's just not been updated.
> We should push up an update with both of the items below.
> Can you lgo a Jira ticket please?
> Thanks
>
> On Mon, Apr 18, 2016 at 7:50 PM, <
> dev-digest-h...@htrace.incubator.apache.org> wrote:
>
> >
> > From: Mike Drob <md..
HTrace Devs,
I was browsing the project site[1] and noticed that it is very very old,
having been last published over six months ago. However, there has been
good activity on the HTRACE-350 Developer Guide and HTRACE-352 Dependency
Info. Am I looking at the wrong page? Does my browser somehow
21 matches
Mail list logo