I'm not clear on why we are removing stats gathering capability. Do we know that customers aren't using this? Is it badly broken?
What is actually driving this work? -- Mike Stolz Principal Engineer, GemFire Product Lead Mobile: +1-631-835-4771 On Mon, Nov 20, 2017 at 11:42 AM, Bruce Schuchardt <bschucha...@pivotal.io> wrote: > Should this be done for the Java caches as well? > > > On 11/17/17 11:48 AM, David Kimura wrote: > >> I agree, a statistics interface seems beyond the scope of Geode Native >> client responsibility. Hiding or removing seems appropriate to me. >> >> Thanks, >> David >> >> On Fri, Nov 17, 2017 at 11:29 AM, Ernest Burghardt >> <eburgha...@pivotal.io> wrote: >> >>> +1 for removal >>> >>> On Thu, Nov 16, 2017 at 1:46 PM, Jacob Barrett <jbarr...@pivotal.io> >>> wrote: >>> >>> I want to open a discussion regarding the removal of StatisticsFactory >>>> and >>>> related APIs from the public API. I can't see that we would want the >>>> Geode >>>> Native client to be a first class statistics/metrics gathering API. >>>> There >>>> are plenty of other first class players in this space. If this isn't a >>>> feature of the client then I suggest it be moved internally. It’s highly >>>> unlikely it’s being used but in the case that it is we can consider >>>> moving >>>> it back after some serious refactoring as it relies on an over >>>> abundance of >>>> raw pointers. Rather than spend time refactoring it now let’s just hide >>>> it >>>> away. >>>> >>>> -Jake >>>> >>>> >>>> >>>> >>>> >
