You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by GitBox <gi...@apache.org> on 2019/09/26 21:27:04 UTC

[GitHub] [accumulo] EdColeman commented on issue #1376: Add gc metrics reporting

EdColeman commented on issue #1376: Add gc metrics reporting
URL: https://github.com/apache/accumulo/pull/1376#issuecomment-535692730
 
 
   > I'm not a fan of doing this in a maintenance branch. This has a strong feeling of new feature, and not a stabilizing bug fix change. We've flexed on this in the past, but the more it happens, the more I'm opposed. We really should stop doing new development on maintenance branches.
   
   We need to discuss a way forward.  Until the 1.9.x branch is declared EOL, there should be a way to improve that code-base.  The metrics are a real pain point for some and up and until they move forward with a 2.x baseline, then improvements should be possible. 
   
   Because of the jump between 1.9.x and 2.x that is required by users, there are going to be people using the 1.9.x line for a while.  Maybe a solution is these types of changes go into a 1.10 release?  The goal would be to offer improvements without requiring all of the client code re-work that is required for a jump to 2.x.  And while back-porting could be done, it is safer for the users if it is in the baseline so that they can count on it being in future releases.
   
   I understand the concern about merging this forward, but that's "my problem" and I'll need to work though changes that are necessary to provide the same functionality across all supported versions.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services