Enis Söztutar wrote:
Bumping this up in case people are interested.
Also this is not coprocessor-specific, because I think we can incrementally
start using the new hbase-metrics module, and get rid of our complicated
metrics2 based patterns for core metrics as well. We should of course start
e
plan is to get off of Hadoop Metrics2, so I am in favor of
>>> either
>>> (2) or (3). Specifically for (3), I believe there is an implementation
>>> for
>>> translating Dropwizard Metrics to Hadoop Metrics2, in or around Avatica
>>> and/or Phoenix Query Ser
tion for
>> translating Dropwizard Metrics to Hadoop Metrics2, in or around Avatica
>> and/or Phoenix Query Server.
>>
>> On Fri, Nov 11, 2016 at 3:15 PM, Enis Söztutar wrote:
>>
>> HBase / Phoenix devs,
>>>
>>> I would like to solicit early f
+1
We also need to get away from Guava's Service interface for replication
endpoint plugins using this same approach (#2): HBASE-15982
On Mon, Nov 14, 2016 at 10:37 AM, Gary Helmling wrote:
> >
> >
> > My current feeling is that external API should never include
> > classes/interfaces which you
>
>
> My current feeling is that external API should never include
> classes/interfaces which you don't "own". Re-building the API that
> already exists is pedantic, but I think it's a really good way to pay
> down the maintenance debt (whenever the next metrics library "hotness"
> takes off).
>
>
/or Phoenix Query Server.
On Fri, Nov 11, 2016 at 3:15 PM, Enis Söztutar wrote:
HBase / Phoenix devs,
I would like to solicit early feedback on the design approach that we would
pursue for exposing coprocessor metrics. It has implications for our
compatibility, so lets try to have some consensus. Add
Söztutar wrote:
> HBase / Phoenix devs,
>
> I would like to solicit early feedback on the design approach that we would
> pursue for exposing coprocessor metrics. It has implications for our
> compatibility, so lets try to have some consensus. Added Phoenix devs as
> well since th
HBase / Phoenix devs,
I would like to solicit early feedback on the design approach that we would
pursue for exposing coprocessor metrics. It has implications for our
compatibility, so lets try to have some consensus. Added Phoenix devs as
well since this will affect how coprocessors can emit
