accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Drob <>
Subject Re: Backwards compatibility of traces
Date Mon, 07 Apr 2014 15:05:59 GMT
Can you give an example of where this happens?

On Mon, Apr 7, 2014 at 10:54 AM, John Vines <> wrote:

> Given our support of backwards compatibility, does anyone have a preference
> for how traces are stored?
> I ask because I have noticed some places where our internal trace hooks are
> named with collisions so that you get multiple events with the same
> identifier which are actually different events. I would like to change
> them, ideally for 1.5.2 and 1.6.1(0?) simply because it's hampering the
> ability to do performance testing and tuning.
> But I'm not sure if A. we're okay making these changes from a compatibility
> perspective and B. we're okay making these changes as part of a minor
> release.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message