xushiyan commented on pull request #1732: URL: https://github.com/apache/hudi/pull/1732#issuecomment-646856565
> > > Understand the issue originates from `MetricRegistry` not allowing update value for existing metric. By the class design, it does enforce the immutable nature of it. A clean impl. could be to update `Gauge<T>` itself. I see `MetricsSource<T>` is wrapping the update logic to serve a similar purpose, which is fine. > > > After some searching, I found that there is a recent upstream PR to implement the "settable" version of `Gauge` > > > [dropwizard/metrics#1599](https://github.com/dropwizard/metrics/pull/1599) > > > which seems to solve the problem right away. > > > IMO we should wait for the upstream change and make small adjustment by using the `SettableGauge`. WDYT? > > > > > > I feel ok, but I’m not sure when it will be resolved. > > Would you please verify it in deltastreamer continous mode? @shenh062326 I think we would fix it in hudi opensource if the PR [dropwizard/metrics#1607](https://github.com/dropwizard/metrics/pull/1607) would not get released in next few days. cc @xushiyan Yes if the upstream takes some time, we should go ahead with the fix. In that case, I think it'll be beneficial to mimic the approach in that PR, which looks like a clean solution, and make it a smooth migration/clean-up once upstream change is released. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
